Sarah Terry

LogicMonitor Staff
  • Content count

    191
  • Joined

  • Last visited

Community Reputation

20 Excellent

1 Follower

About Sarah Terry

  • Rank
    Community All Star
  1. 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).
  2. 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.
  3. 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"}
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. API - Add Instance Count as Datasource Property

    @Brandon thanks for posting. One way to do this programmatically is to make a GET request to get the datasources associated with a device, and filter for instanceCount = 0. There's a similar example on this page: https://www.logicmonitor.com/support/rest-api-developers-guide/v1/datasources/get-datasources-associated-with-a-device/, but you would have to make the request for each device.
  10. netflow data access via API

    @Mosh @mnagel We will publish the ability to get netflow data with v2 of the API, which is coming soon. v2 is not quite ready to be published yet, so use it with caution until it's officially published (it is subject to change), but we should be ready in the next couple of releases - stay tuned!
  11. @Joe Tran interesting - it may be a permissions issue. What permissions do you have specified for Elastic Beanstalk? With the following permissions, I'm seeing tags discovered for the cloud resource representing the environment itself: "elasticbeanstalk:DescribeEnvironments", "elasticbeanstalk:ListTagsForResource",
  12. Hi @Archana - You're on the right path. The best option to get data out of LM is to use the REST API: https://www.logicmonitor.com/support/rest-api-developers-guide/v1/data/get-data/. You can write a script that makes these API requests to get data out of LM, and then sends it to your other tools.
  13. Hi @Joe Tran, Tags should already be added as properties for both Elastic Beanstalk and Lambda - are you seeing cases where this isn't happening? Thanks, Sarah
  14. Pulling Interval At Group Level

    Hi @Joe Williams - You can already do this with a custom property set at the group level, per https://www.logicmonitor.com/support/devices/device-datasources-instances/can-i-customize-data-collection-intervals-for-a-device/.
  15. API - GET 'Expired' SDTs

    @Joe Tran @CBU BA DUDE Yes - this will be available with v2 of our API, which we're expecting publish in one of the next few releases.