Sarah Terry

LogicMonitor Staff
  • Content Count

    204
  • Joined

  • Last visited

Community Reputation

20 Excellent

1 Follower

About Sarah Terry

  • Rank
    Community All Star

Recent Profile Visitors

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

  1. Good catch @Joe Tran! We should be able to break out the listener count into a separate DataSource that applies to each ELB.
  2. Sarah Terry

    Alert Report

    Hi @Ashwini - Yes, there is a limit of 30,000 alerts per Alert report, and the report should indicate that you've hit the limit. The best way to get more alerts, is to run multiple reports with different criteria (e.g. by group, or a few groups at a time).
  3. Sarah Terry

    REST API - Export Dashboards

    @nrichards Yes! The resources & methods are all auto-documented on this page: https://www.logicmonitor.com/swagger-ui-master/dist/
  4. @mnagel We can definitely update documentation to make that clearer - thanks for the feedback!
  5. @mnagel LM Service Insight is an add-on feature - I've just enabled a trial of it for your account, so you should see it now.
  6. Sarah Terry

    REST API - Export Dashboards

    @nrichards Yes! You can use v2 of the API to GET /dashboard/dashboards/ID?template=true, and the response is a JSON export of the dashboard (the same content you'd get from exporting the dashboard from the UI). Let us know if this doesn't solve your problem.
  7. @mnagel Alerting on data aggregated across multiple hosts is now supported with LM Service Insight (released yesterday). More info on these pages: https://www.logicmonitor.com/support/about-lm-service-insight/ https://www.logicmonitor.com/lmservice-insight
  8. Sarah Terry

    Device Group membership

    @Tanvir devices already have a property system.staticgroups that can be used to match group membership in a custom query. Additionally, properties set at the group level will be inherited by the devices within that group.
  9. @Joe Tran @Mosh yes - glob search currently isn't available, but should be fixed with the next release. Sorry about that!
  10. Sarah Terry

    Status Codes recorded in website checks

    Thanks for the feedback @Matt K! The current website status codes are intended to identify more than just unexpected HTTP status codes, e.g. unexpected response content, but I think we can probably add a new datapoint that monitors raw HTTP status code to satisfy this use case.
  11. Thanks @Joe Tran! We should be able to add support for filtering on startEpoch/endEpoch for historysdts, as well as publish the endpoints for websites & website groups. We'll add those into an upcoming release.
  12. Sarah Terry

    Additional Checkpoint locations

    @Joe Tran we can definitely take that into consideration, thanks for the feedback!
  13. Sarah Terry

    Additional Checkpoint locations

    @Joe Tran The LA checkpoint is particularly burdensome for us to maintain. We do plan to retire it, but expect to be able to add new checkpoint locations in the upcoming year as well. We'll definitely look at requests such as the ones in this thread to determine where those new checkpoints should be added. Re the LA checkpoint retirement notice, are you anticipating the SF checkpoint to be insufficient for California / West Coast US based website monitoring coverage?
  14. Sarah Terry

    Additional Checkpoint locations

    @Dave Smale you can actually use LM Collectors as checkpoint locations now - you just need to create an Internal Web Check to do so (instead of a regular, external Web Check).
  15. Sarah Terry

    Swagger Doc

    Yes! We've implemented Swagger for v2 of our REST API and will release API v2 (documented with Swagger UI) and Python & Go SDKs (generated via Swagger Codegen) before the end of the year. We're still looking into whether it makes sense to directly post the JSON Swagger doc, as we did have to customize Codegen to accommodate a few complexities with the API.