All Activity

This stream auto-updates   

  1. Today
  2. Hi, This is really annoying. I have to set custom alerts for our data sources for things like VMware data source usage. The default data sources only give you an error alert when the disk gets to 99% not a critical. I always change this as a data source filling up will take your Vm's offline. I do this for quite a few other alerts too. I then see a new VMware data source that you guys put up and get excited and apply it strait away....overwriting my custom alerts. This normally results in an outage because we didn't notice a data source filling up and a phone call from my boss. so my feature request is...can you guys allow us to 'write protect' our custom alerts so we can import new data sources preserving our custom alerts or changes? Please???
  3. Last week
  4. I too need this. At the moment we have to use two NOC widgets, which of course uses up more screen real-estate, especially if you just want to wadd one item to a NOC widget.
  5. I hadn't noticed that until now! There should be an option to disable sound for alerts on devices that are within an SDT period.
  6. Collectors can be installed using Nano/Small/Medium/Large configurations. Please add a column in Settings->Collectors to show this.
  7. when trying to add a NOC widget under a dashboard you have to choose between a device or a service. right now you can not mix services and device components under one NOC widget. it would be great if that can be fixed. thank you
  8. Thanks Brandon - You are correct - one of the datapoints 'bgrewriteaof_in_progress' reports No Data. The datapoint uses a regex of 'bgrewriteaof_in_progress:(\d+)', and certainly in the environment I was working on, this regex does not match any value returned by the INFO command (or even an INFO ALL command) on Redis version 3.2.8 . From the Redis documentation, the nearest similar return value I can locate is 'aof_rewrite_in_progress', but I do not have a high confidence level that this is the value that the datapoint should be reporting.
  9. It would be good to be able to set AlertRules based on DataSourceInstanceGroups and DataSourceInstanceProperties
  10. Services should support IPv6. Currently, they do not.
  11. As well as filtering based on DataSourceInstanceGroups, it would be good to be able to filter based on DataSourceInstanceProperties. The same is true for alert rules, it would be good to be able to set an AlertRule based on both DataSourceInstanceGroup and DataSourceInstanceProperty.
  12. Currently, Alert sounds are persistent even when an instance is placed in SDT. We need functionality added to suppress all alert sounds while an instance is in SDT.
  13. Hi I would like to see the ability to adjust the font on widgets( specially the table one) is too small when displaying data in TVs
  14. Britt May 25, 09:43 CDT I'm trying to create All Regions_Network dashboard and would like to filter on the alerts. I only want to see on the map UP/Down. Is this possible? also, would like to filter map on Escalation Chain. We only want to see Red/Green. I have added and filtered the alert widget but need the filter on the map.
  15. I'm not sure where else to post this, but I wanted to make sure the LogicMonitor team takes another look at the apache solr datasources in the repository as they need to be scrubbed. Currently these datasources use applies to rules that seem to be very specific to one customer. Here is one example: contains(system.groups,"SEARCH/CHI/SLAVE/JOB") or contains(system.groups,"SEARCH/AMS/SLAVE/JOB") or contains(system.groups,"SEARCH/QTW/SLAVE/JOB") or contains(system.groups,"SEARCH/CHI/MASTER/JOB") or contains(system.groups,"SEARCH/AMS/MASTER/JOB") or contains (system.groups,"SEARCH/QTW/SLAVE/JobAux") or contains(system.groups,"SEARCH/CHI/SLAVE/JOBAUX") or system.displayname =~ "solrone" I should also mention that I have completely rebuilt these datasources and combined them into a single datasource that pulls all of this data with a single API query. I'll be submitting it after I scrub and polish it.
  16. HCPFGA The default LogicMonitor datasource names the instances in a strange way and then alerts for events that have already completed. I've added a better instance naming convention that clearly identifies the event that will occur and when. I also put in logic to detect if the scheduled event has already taken place to prevent unnecessary alerting.
  17. NZRCTG This datasource will automatically connect to your BigFix server and gather a count of the fixlets that need to be applied. This uses the BigFix REST API and requires the following device properties to be set: bigfix.url - The URL of your bigfix server (for example: "bigfix.contoso.com") bigfix.port - The bigfix API port (default is 52311) bigfix.user - Specify a read-only user with the proper rights as documented here: https://developer.bigfix.com/rest-api/prerequisites.html bigfix.pass - The password for the bigfix account you are using The datasource does not have any alerting set up, but you can set your own thresholds.
  18. Kudos! I actually noticed the same thing a few months ago - and like the lazy community member I am - I fixed it without actually submitting it in to the forums or sending it to LogicMonitor to have the repository updated. If I remember right, there was also something wrong with one of the datapoints as well - although that could have been the RabbitMQ datasource. I'm going to try to be better about getting these uploaded.
  19. Currently we cannot select a Custom Time range less than one hour. Can you please change it to enable us select time frames less than one hour?
  20. I AGREE THIS WOULD BE AWESOME LETS MAKE IT HAPPEN ALRIGHT GUYS?
  21. LM Dev's, I would like to be able to run a report over multiple interfaces representing total bandwidth used cumulatively for example. I have 13 offices with 1 mpls connection at each office. I would like a report that would show me the total per day mpls traffic for the 13 offices as one line in a chart/graph over the course of say 3 months. To determine if I can see company wide trends in utilization. please let me know if you have any further questions. Thanks, Ben
  22. I just spent a lot of time beating my head on this, and found the problem is that instance groups are not really groups, they are just stored as labels on instances. As such, they themselves have no place to store additional information, like device groups can. In addition to the above desirable features, it should be possible to set alert expressions on instance groups that are persistent (like for device groups). I ended up dealing with the latter issue via the API, so now I can do this: ./lm-set-alertexpr --company mycompany --devicegroup "All Exchange Servers" --datasource "WinVolumeUsage-" --datapoint "PercentUsed" --instancegroup "MailboxDB" --instancegroupop '!:' -v -n --alertexpr "> 90 95 99" So at least some issues can be resolved via the API, but alert routing via instance group is definitely needed! Anywhere an instance can be used, an instancegroup should be also possible, definitely. Regards, Mark
  23. Thanks Kerry. That worked like a charm.
  24. Hi Tom, We don't currently allow for reports to be sent out multiple times per day, however, you can create the report you want to see, save the initial copy with a descriptive title, and then any subsequent changes made to that report will prompt you to save as a new report, or to overwrite the old one. So you could create "Report X 8:00AM" - and then go in and edit the scheduled time and report title to something like "Report X 4:00PM" - save it as a new report, and that should effectively accomplish what you're looking for. Let me know if you have any questions or concerns... Thanks! Kerry
  25. I have also noticed an oddity. If you add a note to the alert and save it, then go back in to Ack the alert, the Ack dialog does not contain the note, so you have to type it in again. Ack should pick the last note added.
  26. Earlier
  27. I previously published a datasource for Tesla Motors Battery Statistics - which presents compelling vehicle battery and charging information that is fetched from the Tesla REST API. To complement those efforts, I've written a few other Tesla Motors LogicModules that return a variety of different, but still interesting, datapoints - including a ConfigSource that displays configuration information about the vehicle itself (are the doors locked? Is the sunroof open?) The following is a list of all the Tesla Motors LogicModules now available (see the above-linked post for additional info on how this all works.) DataSource 'Battery Statistics' tracks battery and charger performance and health metrics (previously posted to the Exchange but included here for sake of keeping everything together.) The datasource name is TeslaMotors_BatteryStatistics and has lmLocator DXLLKY. DataSource 'Climate Statistics' tracks inside and outside temperatures, as well as driver and passenger temperature settings. The datasource name is TeslaMotors_ClimateStatistics and has lmLocator YZRWXC. ConfigSource 'Car Configuration' collects textual configuration data, cleans it up and makes it easily readable (screenshot attached.) The configsource name is TeslaMotors_Configuration and has lmLocator GRY9AE. DataSource 'Location Data' tracks compass heading, latitude and longitude, and power. The datasource name is TeslaMotors_LocationData and has lmLocator AYWYWA. DataSource 'Odometer Reading' does exactly what you might expect. The datasource name is TeslaMotors_BatteryStatistics and has lmLocator HHJRDJ.
  1. Load more activity