All Activity

This stream auto-updates   

  1. Yesterday
  2. I also have scenarios where I would like to schedule a datasource to only run at a certain time of the day - maybe like Windows Task Scheduler. Example - Pulling disk defgrag reports overnight. With large volumes, this may take a while to execute. I'd really only want to execute it overnight - or maybe even once a week. I know I can set the ".pollinginterval", but I can't make it execute at a certain time. It's still a bit arbitrary on when it does the 1st check, which then determines the time for all future checks.
  3. @Brandon this is correct and the list can be truncated. The property source character limit is 2,000 currently. I created something very very similar on my portal a while back, and here's the proof the list can get truncated: Note, on this particular device there is a "WalletService" service, and of course Windows Firewall. Here's what the end of the property source (that lists services alphabetically) looks like: Note the property source value ends "WalletS" - a truncation of "WalletService" - and Windows Firewall is absent.
  4. The Add a new chain > Add new recipients dialog seems to suggest that only users can be added, but in fact allows groups also. Please enhance the UI captions to make clear if one or both is possible. It's confusing to my users and generates unnecessary tickets.
  5. Last week
  6. The attached images show the CPU utilization when a Collector starts to collect configurations for our devices. We would like to have more options to stagger the collections of device config throughout the day. When the collections are all attempted at about the same time we see the CPU utilization jump and also get many failed collection warnings. Please make it so that we can specify different collections times for groups of devices.
  7. Agree with Tom, a checkbox to disable monitoring for a device or group during the SDT time period.
  8. Hi Shaun, LogicMonitor's REST API devices resource includes the name (hostName, IP/DNS), displayName & id. Though the REST API operates based on resource ids, you can still filter your request by displayName, name, or any other parameter - so you should be able to get the same information as the RPC API (and actually the REST API provides more powerful filtering than the RPC API). You are correct that filtering by name as you've done may return more than one result - you can avoid that by (1) filtering by displayName instead, as that is guaranteed to be unique (e.g. ?filter=displayName:prodServer123) or (2) adding preferredCollectorId to the filter, as the name/IP is guaranteed to be unique for a given Collector (e.g. filter=name~8.8.8.8,preferredCollectorId:9). Does that answer your question? If not, can you provide the RPC request you're making that you're trying to replace with REST? That will help with context. Thanks, Sarah
  9. Currently there is no hostName parameter available for the REST API though it exists in the RPC API. When retrieving information about a device using the 'devices/device' endpoint using the REST API: /devices/device/?filter=deviceType:0,name~<some ipv4 address>,size:1 There is a chance that the device being returned is actually another device when using the ~ operator against the name of the device. There would be quite a bit of work to wildcard filter by name and would be different depending on the tenant's naming schema. Adding the hostName parameter as a feature would mirror RPC's functionality and save quite a bit of custom code from being written. If anyone is aware of how to filter by hostName or similar (ipv4) parameter without additional operations please let me know.
  10. I tried to use the LM Exchange ID 2WHYY4, and the system could not find the datasource. I was wondering if you had a new ID?
  11. Thanks for sharing, Tom! Hopefully we can make it a bit easier to get this information in app / via API moving forwards
  12. There are ways to set this via an alert. We use a complex formula to determine if a device stopped reporting data: if(un(CPUUsage),if(un(CPUUsage1),if(un(MemoryActive),if(un(DataRateRx),1,0),0),0),0) Using this will give us the ability to create an alert, this would then give you the ability to pull alerts from the API and tell you what devices are no longer reporting data properly (or an alert report via the reports section). We just set this as a warn for visibility.
  13. This would be a great addition to SDT, down devices tend to load up collectors with failed task rates. Adding a check box to disable monitoring during SDT would be optimal as we have some locations that go offline for extended periods of time and contain a large amount of devices that will cause collector performance issues. Maybe all it does is leave "ping" monitoring enabled so we continue to get the host down part, but all other datasources are suppressed if you click the checkbox.
  14. Sorry Mosh,but I was proud of my work on your ticket, so had to tell the world ! I wll leave you to post the others, if you need a hand on the snmp one let me know.
  15. Please add option to filter severities on the Map Widget. We only want to show amber (P2) or red (P1) on our maps.
  16. I came here to post this today. You beat me to it! Doing the same for Linux now, though haven't quite got the SNMP equivalent (by volume name) quite working yet.
  17. Please make it so that the Add New Group dialog inherits the default collector from the parent group if the parent group has a default collector set. We add groups all the time, so this would save us two or three mouse clicks each time.
  18. 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 critical applications) E: 1 TB (Backups) F: 510 GB (Other Applications) A 90% alert will give you a critical at 1GB,50GB,100GB and 51GB respectively. Now the C: drive may be a cause for concern, but the others not so much. The two application drives you might only be concerned if they have less than 4GB free and the backup less than 10GB. So, we decide to alert on the following C: freespace is <1 GB D: freespace is <4 GB E: freespace is <10 GB F: freespace is <4 GB You could clone the datasource so you have four copies one for each drive but this is harder to maintain in the future and does not scale well. It would be better if you could somehow get the drive letter and assign a threshold based on that. Logicmonitor’s scripted complex datapoint using groovy to the rescue. The disks datasource queries the class Win32_Volume. We need to use the raw drive letter output from the WMI class so would write a groovy script like: Drive=output["DRIVELETTER"]; return(Drive); This returns C:,D:,E: and F: Not much use as Logicmonitor doesn’t deal with text, only metrics. Let’s beef up the script. drive = output['DRIVELETTER']; freeSpaceLowerLimitGigabyte = '0'; if (drive == 'C:') {freeSpaceLowerLimitGigabyte = '1';} if (drive == 'D:' || drive == 'F:') {freeSpaceLowerLimitGigabyte = '4';} if (drive == 'E:') {freeSpaceLowerLimitGigabyte = '10';} return freeSpaceLowerLimitGigabyte; This returns 1,4,10 and 4 for each drive, now we have a complex datapoint that returns the lowerlimit in GB for each drive dependant on the drive letter. Again, we can’t alert on this so we need another datapoint So we can use this to check if freespace is less than the freeSpaceLowerLimitGigabyte. To do that create a CapacityAlert datapoint using this expression if ( lt (FreeSpace, FreeSpaceLowerLimitGigabyte * 1024000000) , 1, 0) Which breaks down as if freespace is less than the assigned limit for that drive letter then return 1 (which you alert on.) Otherwise return 0. Alert threshold set at = 1 1 1, and we get critical alerts if: C: freespace is <1 GB D: freespace is <4 GB E: freespace is <10 GB F: freespace is <4 GB
  19. Thanks for the post. I helped a lot. noyasystem
  20. @Jake Cohen nice stuff.
  21. EnviroMUX datasources (built/tested on Enviromux SEMS 16): 1) EnviroMUX Battery: MXDPZZ 2) EnviroMux Digital Inputs: 33JLN4 3) EnviroMux External Humidity Sensors: FAK6PD 4) EnviroMux External Temperature Sensors: JZFJZJ 5) EnviroMux External Water Sensors: 9FKWZN 6) EnviroMux Internal Humidity: NDW6AW 7) EnviroMux Internal Temperature: G2Y4GL 8) EnviroMux Output Relays: CAE3TN 9) EnviroMux Power Supplies: 2TYPZC
  22. Exactly what we are trying to accomplish...we are dealing with close to 5K devices and need to know quickly if devices which were working are now reporting "No Data" Thank you!
  23. hi Kaushal, you can use this datasource if you can add the ELB as a device.
  24. Could we have an option in the device/manage screen to stop the device being monitored by all data sources? When this option is selected, the device will show with a different color.
  25. Is there a way to run a report for anything reporting "no data"?
  26. Hi Todd, There isn't an easy way to pull devices with instances reporting "No Data" (in the UI or via API) - you can do it based on alerts if alerting is set up for No Data, or the long way by iterating through current data for instances, but there's no great solution right now. It has come up before, so we are exploring what a better solution would look like. Are you just looking to flag devices that aren't reporting data for possible misconfigurations (on LM or device side)? Any additional context you can provide will help us come up with the best possible solution. Thanks, Sarah
  27. Hi @Mahlon Greene, the issue of false alerts when the uptime counter wraps has recently been fixed. If you update from the repository you should see an update for "Host Uptime-". The datapoint "Uptime" in the new version will still be incorrect after the counter wraps, but there is logic in the Complex Datapoints that will prevent an alert on a counter wrap while still alerting on an actual reboot. -Michael
  1. Load more activity