Sarah Terry

LogicMonitor Staff
  • Content Count

    233
  • Joined

  • Last visited

Community Reputation

20 Excellent

3 Followers

About Sarah Terry

  • Rank
    Legend

Recent Profile Visitors

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

  1. It's possible if the usage is slowly & steadily increasing that the band will adjust to that usage. You can avoid suppression by having static & dynamic thresholds at separate severities (eg static threshold for critical severity & dynamic for warn | error). Sometimes these metrics where you generally know that certain good and bad ranges always hold true (e.g. above 90% is always bad, below 90% is always good) are a better fit for static thresholds. Dynamic Thresholds are most useful when it is not possible or difficult to identify a range generally/globally across all instances (
  2. @BCO assuming you have a website in LM with the exact name 'sitename.com', you should be on the right track. Though, in v2 of the API you should enclose filter values in double quotes (per https://www.logicmonitor.com/support/rest-api-developers-guide/), so try '/website/websites?filter=name:"sitename.com"'.
  3. @Mosh That is a great point, and one our team uses as part of our follow-up tasks when conducting a Root Cause Analysis (RCA). As much as we strive to monitor everything, gaps may be discovered. To resolve those gaps we have a two-pronged approach. We identify application logic to see if they can be modified to self-recover from a failure. Secondly, we identify ways to have DataSources monitor and alert upon these issues in the future. This cycle is performed consistently with all Service Disruptions. Apologies for the inconvenience as experienced.
  4. Apologies @Mosh - the issue should be resolved now: https://status.logicmonitor.com/incidents/79scd0n8xgms
  5. Hi @starboy9 - There should be more than 3 TopologySources at this point, and our team is frequently releasing new TopologySources with additional coverage. To get started, you just have to make sure you have the most up to date modules in your account - this page provides getting started instructions: https://www.logicmonitor.com/support/topology-mapping/topology-mapping-overview/. Let us know if you have trouble getting started or additional questions!
  6. @gwengrafana the resource path should be: $resourcePath = '/device/devices/465103/devicedatasources/8252658/data to get data for all instances of the Ping DataSource. The Ping deviceDataSourceId in this case is the 8252658.
  7. @gwengrafana there is an example on this page that shows how to get raw data via the API: https://www.logicmonitor.com/support/rest-api-developers-guide/v1/data/get-data/ Getting data for Ping is the same as getting data for any other DataSource, so that example does apply. Your approach looks correct, but make sure you're using the correct Id - you need the deviceDataSource Id, *not* the DataSource Id. /settings/datasources endpoint will only return the Ids of the DataSources in your account, but what you want is the Id of the instantiated Ping DataSource for a given device. If you inste
  8. Yes @Cole McDonald - you can just update that field with a PATCH request & data collection tasks should immediately start being scheduled with the new collector
  9. @Cole McDonald just update the preferredCollectorId for the device (not the system property, but the actual preferredCollectorId field)
  10. @Cole McDonald all system properties are read only, except system.categories (idea being they are set by the "system" - LM). But many of those system properties are set based on the device attributes that you can configure directly, e.g. displayName, preferredCollectorId, etc.
  11. Hi @Cole McDonald - For the query parameters, it should be "?filter=preferredCollectorId:$($fromHost.id)". It's explained here: https://www.logicmonitor.com/support/rest-api-developers-guide/v1/devices/get-devices/. Are you looking at the Swagger docs for v2 of the API? Thanks, Sarah
  12. Hi @starboy9 , The edges are discovered by TopologySources. The TopologySources are usually using some discovery logic (e.g. SNMP, API) to discover edges for monitored resources with ERIs (external resource Ids). The ERI properties are typically populated by PropertySources or DataSource AD scripts. So to ensure edges are discovered (and therefore available for display in maps), you need to ensure you have: 1. imported TopologySources into your account (Settings | LogicModules | TopologySources | Add | From LogicMonitor Repository) 2. imported PropertySources into your account
  13. @Cole McDonald @Joe Tran we will improve the documentation for this endpoint - thanks!
  14. @Soma Sekhar I think the issue here is the graph Id - in the API response you included, the graph legends do not match the legends in the image. So the graph Id in the request must not be the right one. You can make a GET request to /device/devices/{deviceID}/devicedatasources/{deviceDataSourceID} To see all graph Ids.
  15. @Soma Sekhar can you provide an image of the graph you're trying to get data for? It looks like the request was successful, and that the graph itself just doesn't have data.