Sarah Terry

LogicMonitor Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

20 Excellent

1 Follower

About Sarah Terry

  • Rank
    Community All Star
  1. instance equivalence groups

    @mnagel we're working a feature for exactly this At a high level, we'll let you group together instances across devices & then aggregate data across those instances and alert on the aggregate data. This should be helpful in clustered setups such as the example you've described, as well as more ephemeral environments where the aggregate data will provide historical data as devices & instances are being added / deleted from LogicMonitor.
  2. Audit Log Enhancement for API Activity

    Hi @stuart.vassey - thanks posting. Follow up question: If we offered a way of monitoring API usage (in a granular way that exposed the number requests to resources by method & type) for users in your account, would you still want the GET requests logged in the audit log?
  3. Option to disable deleted devices

    @Mosh got it. We're thinking it might be better to remove deleted devices from being counted towards the unique IP requirement to resolve this issue, vs forcing a permanent delete every time. Is your workflow to delete via API or are you manually deleting in the UI?
  4. Option to disable deleted devices

    Hi @Mosh - Thanks for the feedback. Devices in the recently deleted devices section are permanently deleted after 7 days, so you shouldn't need to make that additional mouse click. Do you have a concern with leaving the recently deleted devices in that transition area for 7 days? Thanks, Sarah
  5. isLinux() is false for ec2 instances added automatically

    @Sam Gendler the instances added via your cloud account shouldn't be handled differently. Once assigned, the local Collector should run Auto Properties to categorize the instance and populate system.sysinfo. The device should get the snmp system.categories values and match the isLinux() function at that point. Were SNMP credentials added / inherited for the device? You might try running Active Discovery manually & seeing if the instance gets categorized then (though there should have been a run auto triggered):
  6. LM Websites API - auth password should be masked

    @Joe Tran Agreed - we'll fix that (we can mask the password value in the auth object just like we mask sensitive device property values).
  7. REST API - Get device history

    @Keimond are you looking just for alert history for a particular device? You can see alert history at the alert level - on the Alerts page or on the Alerts tab for a resource, you'll see a history tab when you select an alert: But the history is tied to the alert, not the device or instance itself. The ability to retrieve this info isn't published for our REST API, but we could publish it. The other option would be to query alerts for a particular device, and look at only cleared alerts that occurred during a specific time window - so the request might look like: GET /device/devices/1/alerts?filter=cleared:*,endEpoch<1524170891,startEpoch>1523567577 And that'd show you alerts that occurred for device 1 in the past week. Do either of these help with the information you're trying to get?
  8. Sum across DataSources and dynamic alert levels

    We're working on a feature that will enable much more flexible alerting across DataSources and Devices, and should address this request. At a high level, we'll allow you to group together instances across devices and set aggregate thresholds for the group - one of the primary use cases is better alerting for clustered resources.
  9. cluster alert improvements

    Hi @Joe Tran and @Keimond, We're working on a feature that will enable much more flexible alerting for instances across devices. At a high level, we'll allow you to group together instances across devices and set cluster-like thresholds for the group. So to make it based on instance names, you'd group together instances based on name (can be across multiple devices) & set aggregate thresholds for each group. Can you provide more detail re what you're alerting on in these cases? Thanks! Sarah
  10. API/Script

    @Tanvir the resource path should be '/device/groups', and you should add an item to the data payload 'parentId' set to the id of the servers group. This will ensure that the new Fileserver group gets added underneath the servers group.
  11. Monitor AWS Reservations

    @nathan.wilkerson This is available now with the AWS_EC2_Reserved_Instances DataSource
  12. API - GET 'Expired' SDTs

    Hi Patrick - We should be able to publish the ability to query historic SDTs via our REST API in an upcoming release. Thanks, Sarah
  13. @Josh Jacques We don't have an ETA yet, but are hoping to get it out in the next few months
  14. getGraphImage REST API call

    Hi @beakynb - We don't currently offer options to specify image size and title, but we can add them.
  15. @Josh Jacques @Joe Tran yes, this is coming with v2 of our REST API