Search the Community

Showing results for tags 'Datasource'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LogicModule Exchange
    • LM Exchange
    • LM Staff Contributions
  • Product Announcements
    • LogicMonitor Notices
  • LogicMonitor Product Q&A
    • Feature Requests
    • Ask the Community
    • From the Front

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 38 results

  1. I am not sure exactly how to describe this other than by example. We created an API-based method a while back to control alerting on interfaces based on the interface description. This arose because LM discovered interfaces that would come and go (e.g., laptop ports), and then would alarm about the port being down. With our change, those ports are labeled with a string that we examine to enable or disable alerting. The fly in the ointment is that if an up and monitored port went down due to some change, our clients think they should be able to change the description to influence behavior. Which they should. Unfortunately, because LM will not update the instance description due to the AD filter, the down condition is stuck until either the description is manually changed in LM or until the instance is manually removed in LM. Manual either way, very annoying. My proposal is that there should be a way to update the instance description even if the AD filter triggers. Or a second AD filter for updates to existing instances. I am sure there are gotchas here and perhaps a better way exists. I considered using a propertysource, but I don't think that applies here. The only other option is a fake DS using the API to refresh the descriptions, but then you have to replicate the behavior of many different datasources for interfaces.
  2. ... with exceptionStatus ORA-01013: user requested cancel of current operation That is all. 😅
  3. As I am sitting here, trying to explain to one of our internal partners, for what seems like the umpteenth time, on how to read an alert threshold expression from a ##THRESHOLD## token--it would be great if there were individual message tokens for each of the thresholds. Something like ##WARNINGTHRESHOLD##, ##ERRORTHRESHOLD##, and ##CRITICALTHRESHOLD## that should render the comparison operator and that respective threshold value, example--- This way, I can be more clear as to what this string of numbers actually mean in this type of fashion
  4. The concept of OpsNotes is growing on me. What would really make it shine would be a Groovy helper class/client that can insert an OpsNote from within a Datasource definition for the device context without resorting to using the REST API. Use Case-- we have a datasource for SQL Servers to count the number of blocking sessions on a per database basis. The DBAs want a way to capture some of the session metadata with this metric. OpsNotes seem like a potential way of capturing this.
  5. 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.
  6. For JDBC datasources, please create a token that would enable us to include the JDBC driver exception message in the alert for Query Status data point alerts, the ones that are based on: Query status - 1=ok, 2=credential invalid, 3=connection string invalid, 4=connection rejected, 5=driver not supported, 6=connection failure, 7=query failure This would greatly help us to achieve faster time to resolution of incidents when the exception is code of type 6 and 7.
  7. We have script DataSources that output useful diagnostics information that help Operations to understand the number value when an alert is generated. We want to include the raw output from a DataSource in the alert and email body. What we need is a ##DSRAWOUTPUT## token which contains the complete raw output sent to standard out from a DataSource script. For example, we monitor for processes running under credentials they are no supposed to be running under, and we want to include that info as textual information in the alert/email body.
  8. One of the biggest challenges with LM is the reliance on numbers only in datasources -- the reason is understood, but the result is often messy and many backflips must be done to get a usable result in many cases. I recommend that there be a "lookup" function for numbers that can be associated with datapoints so numeric values can be replaced with text when that is appropriate. An example I just ran into today was after I added the OpenWeatherMap datasource from LM Exchange. It did not include the weather condition, so I added that to the datasource. The values for these range from 200's to 800's indicating "clouds", "rain", etc. You could in theory create a legend for this as is done typically, but the list is too long in practice for 60-odd values (https://openweathermap.org/weather-conditions). If those code-to-string lookups could be defined and referenced, then the value displayed in graphs, in alerts and anywhere else applicable could be displayed as the mapped values, not the original codes. This obviously applies much more widely than this example, but this example shows more clearly how the current method breaks down.
  9. AWS lists that the Listener limit is on a per ELB basis. The AWS_ClassicELB_ServiceLimits datasource seems to intimate that the ListenerUsage is returning the total number of listeners for the given region. Is this useful information to capture on a regional basis or should this be refactored to apply to each classic ELB?
  10. This is my first post in the community, so please let me know if I'm doing anything wrong... I decided to write a datasource that allows you to read in the salient information from a Nest thermostat and alert against it. Namely the current temperature (ambient temp) the target temperature and the humidity. You'll have to create a Nest developer account, and authenticate your account to access your Nest thermostat. Nest's API implementation requires that you create an OAuth access token using something like Postman with your Nest developer account. Step by step instructions to create that access token are here: https://codelabs.developers.google.com/codelabs/wwn-api-quickstart/#4 Once you have that, set both your thermostat ID as well as your access token as custom properties for authentication, nest.accesstoken and nest.thermostatid. You'll put these properties in after you add developer-api.nest.com as a device in LogicMonitor. Assuming everything is correct, you should start getting data. The identifier code in the Exchange: L6MW9T N699G4 Updated with new HTTP commands to use collector rather than the JRE. Let me know if you have any questions about it!
  11. After Marketo's large outage due domain registration expiring, we created a DataSource that monitors the amount of time remaining on a registered domain. https://www.logicmonitor.com/blog/avoid-front-page-news-outage-like-marketo/ Locator ID: HCZPGR
  12. I'm trying to clean up datasources that are in our account that do not have any instances associated with them and likely never will. Currently I have to do this manually by inspecting each datasource in the GUI. It would be really great if the datasource instance count was returned as a property. Even better would be if the instances and associated device ID's were returned as well, but for now I'd be happy with just the device/instance counts.
  13. I cooked up a currency converter for travel a while back. You can add currency pairs as instances and keep an eye on when to buy your holiday money! Data is from the Yahoo Public Finance API (and is often delayed) so I'd advise against using it for Forex! General usage information is in the Technical Notes section of the datasource. LogicModule Locator : FHHPJG
  14. Often when an alert pops up, I find myself running some very common troubleshooting/helpful tools to quickly gather more info. It would be nice to get that info quickly and easily without having to go to other tools when an alert occurs. For example - right now, when we get a high cpu alert the first thing I do is run pslist -s \\computername (PSTools are so awesome) and psloggedon \\computername to see who's logged in at the moment. I know it's possible to create a datasource to discover all active processes, and retrieve CPU/memory/disk metrics specific to a given process, but processes on a given server might change pretty frequently so you'd have to run active discovery frequently. It just doesn't seem like the best way and most of the time I don't care what's running on the server and only need to know "in the moment." A way to run a script via a button for a given datasource would be a really cool feature. Maybe on the datasource you could add a feature to hold a "gather additional data" or meta-data script, the script could then be invoked manually on an alert or datasource instance. IE when an alert occurs, you can click on a button in the alert called "gather additional data" or something which would run the script and produce a small box or window with the output. The ability to run periodically (every 15 seconds or 5 minutes, etc) would also be useful. This would also give a NOC the ability to troubleshoot a bit more or provide some additional context around an alert without everyone having to know a bunch of tools or have administrative access to a server.
  15. Code is TXL3W9 This DataSource provides instances for each of the Network adapters, including the following Instance Level Properties: auto.TcpWindowSize auto.MTU auto.MACAddress auto.IPSubnet auto.IPAddress auto.DNSHostName auto.DNSDomain auto.DefaultIPGateway auto.SettingID auto.Description
  16. I will explain the request here as best I can in a written format but a visual would be simple. By example of FortiGate: We had a requirement to monitor the WAPs (the FortiGate can act as a Wireless LAN Controller (WLC) ) for reporting and performance. Depending upon the size of the firewall 1 through N WAPs can be authorized, configured, and monitored. These devices are visible through SNMP queries against the firewall and offer a rich set of information (CPU, memory, version, SN, model, client associations). Now to the feature - when we added the capabilities it became time consuming to first identify the OID and then repeatedly poll to pin down the elements. So, how about a "button" in the UI next to the OID to walk or poll and display the results? Additionally, how about offering the results and on that page an option to add them in this datasource? Look at the Forti AP definition for what we did and try to visualize the simplicity of having the UI trigger a poll on a device (through the associated collector) to make this a breeze.
  17. Please add native support for discovery of ECS metrics by ClusterName AND ServiceName dimensions!
  18. When cloning an existing datasource and changing the type from one type to another similar type, all of the datapoints immediately disappear. I am overhauling some of my script and webpage datasources where the output is json or key-value pair into batchscript. As soon as I change the collection type, the datapoints immediately disappear and it's like I'm starting from scratch. The script auto-discovery and collection panes also get wiped out. Unfortunately this has translated into me spending a lot of time recreating datapoints instead of modifying existing ones. I understand why those datapoints are not compatible with SNMP or CIM collection methods, but they should largely be transferable between certain datasources. On the bright side - this has forced me to start overhauling my datasources by exporting and importing the XML files. Still, it would be great if the GUI could play nice for some of us power users.
  19. CDP Neighbors DataSource with Instance Level Properties 3TJN72
  20. Please add a test function for JDBC active discovery and colelction, just as you have done for scriped DataSources.
  21. DataSource to monitor summary metrics across all Harvest Projects (https://www.getharvest.com/). LM Locator: 6MZ3HE
  22. Golf enthusiasts! Here's a DataSource to monitor Handicap Indexes over time. LM Locator: 6FDZRJ
  23. DataSource to discover and monitor Harvest Projects (https://www.getharvest.com/). LM Locator: HYXHWP
  24. Hi, I love the idea behind the "no data" warning, but it's missing one thing that I think would help make it a little more friendly. We have a few devices that have spotty collection reliability, and it often times leads to use seeing "no data" warnings blowing up in our alerts console for a few minutes and then disappearing. I'd really love to see an option similar to what exists with the actual data points, that is, only show a "no data" if there's "x" consecutive polls of no data. This would prevent the times where we might miss two polls in a row from flooding the alerts.
  25. When updating datasources from the repository, there should be an easy way to maintain your existing AppliesTo and alert threshold settings.