Sarah Terry

LogicMonitor Staff
  • Content count

    198
  • Joined

  • Last visited

Community Reputation

20 Excellent

1 Follower

About Sarah Terry

  • Rank
    Community All Star
  1. @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
  2. 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.
  3. @Joe Tran @Mosh yes - glob search currently isn't available, but should be fixed with the next release. Sorry about that!
  4. 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.
  5. 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.
  6. Additional Checkpoint locations

    @Joe Tran we can definitely take that into consideration, thanks for the feedback!
  7. 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?
  8. 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).
  9. 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.
  10. Collector REST API Requests

    It's a JSON object that should include the following fields: majorVersion, minorVersion, startEpoch, description. So if you're trying to add a one time upgrade to 27.003, it might look like this: {"majorVersion":27,"minorVersion": 3,"startEpoch": 1538420400,"description":"upgrading to the 27003"}
  11. Collector REST API Requests

    Hey Phil, You can actually do all of those with v1 of the API (via onetimeUpgradeInfo, automaticUpgradeInfo, and customProperties fields, respectively), it's just cumbersome to update the Collector via PUT. With v2 of our REST API, which is about to be released, we'll offer update via PATCH, which should make all three of those actions significantly easier. The v1 API docs can probably also use more detail regarding manipulating those three fields - I can update those. Thanks, Sarah
  12. Hi @Jim - Glad that fixed it! The Collector sizes correspond to different resource requirements, and monitoring capacities - but these are mostly just configuration differences, and won't necessarily impact the size of the installer itself.
  13. Fetching A Specific Dashboard URL

    Hi @Michael Lorincz, The API request you've specified will return the dashboard's unique ID, which won't change for a given dashboard. You can use that ID to construct the full URL - as you've noted, this should be in the format https://companyname.logicmonitor.com/santaba/uiv3/dashboard/#dashboard=ID. Thanks, Sarah
  14. Hi @Jim - Are you using Basic Auth, or LMv1 (token authentication)? If it's the latter, make sure you're not including the query parameters in the resource path for signature calculation. For reference, you can look at how the examples on this page are breaking out the query parameters separately.
  15. Hi @Jim, You can use the following for a Windows nano Collector: /setting/collectors/31/installers/Win64?collectorSize=nano The note in the article is just indicating that the resource path used for token authentication should not include any query parameters. So your request can include query parameters (eg to specify Collector size), but those should not go into the signature calculation. If you don't specify the Collector size via a query parameter, you'll get a small Collector (not nano). Thanks, Sarah