David Lee

LogicMonitor Staff
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About David Lee

  • Rank
    Observer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Mosh, Been a while hope you are okay, and yes thanks for pointing this out, we have already seen this and raised an urgent ticket for resolution, please feel free to hop onto chat for more information if you need it, David Lee UK Team Lead, Technical support
  2. Although this is custom work and normally Support wont be able to assist we have implemented this for other customers and can happily assist you with this request, please open a support ticket when doing so it might help to pass the TSE that answers you my name or a link to this page.
  3. I have published it to the exchange with the locator code of PMWWJN, you can use this code to import it directly into your account
  4. apologies I have been away, I can share it but it will take quite a while to go through security review, it will be faster if you open a chat with support and ask for me or let me know your portal and I can import it for you
  5. We recently had this question asked to support "Is it possible to set conditional alert thresholds for a certain datapoints? For example for all servers, the "AvailableGB" under Disks > Volume Usage > Alert Tuning. If we wanted volumes that are... - Up to 100GB total in size, the alert threshold is 10GB - 101GB - 500GB total in size, the alert threshold is 40GB - 501GB - 3TB total in size, the alert threshold is 200GB - 3TB - 10TB total in size, the alert threshold is 400GB" Out of the box , then no we dont support this. Our standard thresholds would alert
  6. Dan, Thanks for the extra information, another quicker fix would be to clone the snmp64_if and change the discovery type from value to wildcard. This will then work where the normal one fails, but instead of a name interfaces will show the oid value. I.E. instead of FastEthernet 0/4 it might show 17. so not as intuitive to undertstand which interface is which
  7. Recently we have seen a number of issues whith Fortigate not showing interface datasources. With the release of FortiOS 5.4.1 Fortigate changed the behaviour of the description oid. This results in Logicmonitor being unable to discover the interfaces. The SNMP get value for the interface description now returns the value from "set description " instead of the interface name. You must add descriptions to each interface using these CLI commands: config system interface edit set description “<int>” end Once completed, forcing Active Discovery
  8. Configuration backups in LogicMonitor is a great feature to help you be aware of changes being made ,store version history and restore your device configurations. Newer devices are can have subscriptions that pull the latest data from the manufacturer, such as malicious IP address lists. Encrypted information may be re-hashed for added security and these are expected behaviours - NOT a config change. So you need to ignore these changes, as they are not operational changes and you do not need to be woken at 3 in the morning to see that there are some newly added malicious
  9. Hi Ray, As you are no doubt aware you can edit your configsource to ignore certain lines with regex. So you can add an ignore change for lines that contain builldno for example. But stipulating every line except one would be a nightmare and you never know what the lines contain all the time. So flip it on its head. Make an ignore check, select ignore lines with this regular expression and use the expression !("#conf_file_ver=") Basically this means ignore every line that does not contain #conf_file_ver= You can see in my example above I have changed the file version a
  10. You might have received an alert saying your linux based device has just rebooted, but you know that it has been up a long time. A switch might have just sent an alert for every interface flapping when they have all been up solidly. The important question to ask here is how long has the device been up? If its been up for 497 days,994 days,1491 days or any multiple of 497 then you are seeing the 497 day bug, that hits almost every linux based device that is up for a good length of time. Anything using a kernel less than 2.6 computes the system uptime based on the internal ji
  11. Windows Drive Space Alerts By default, LogicMonitor alerts on the percentage used on any drive. This in general is fine, but sometimes not. Let’s imagine you have a 2.2 terabytes drive. You might have your critical threshold set at 90%, which sounds fine, until you realise that you are going to get a critical alert when you still have 220 GB free. In my case that would be a cause for some celebration, not really an urgent need to get up at 3 A.M. and delete files so the world doesn’t end. Now Imagine your 2.2TB drive is divided up as: C: 10 GB (OS) D: 500 GB (Mission cr
  12. Helping us to help you Our job here at Logicmonitor technical support is to help you in your day-to-day work. Whether your report isn’t emailing out, a device is not responding to WMI or you don’t understand why a particular alert is occurring – we’re here to help. But when you submit a ticket it is usually in a queue, being British I love queues! But the support team hate making people wait so anything we can do to make the queue smaller means you must wait less for a response. So here are some tips to help us help you faster. Write a Descriptive Summary
  13. The access log goes back 60 days and you can already download it by pressing the download button at the top right. This gives you a CSV file of the log.