stuart.vassey

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    4

Community Reputation

7 Neutral

About stuart.vassey

  • Rank
    Member

Recent Profile Visitors

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

  1. Forrest, when SLAs are reported as un-met, but it wasn't the service owner's fault, there needs to be a way to not penalize them. For example: 1) When the LogicMonitor platform has an outage (I've seen this happen and created tickets) 2) When a new EA collector crashes or has a bug with script execution (I've seen this happen and created tickets) 3) When the monitoring team accidentally breaks a datasource, which mistakenly marks a service down (this is not uncommon) In all of these cases, SLAs would be inaccurate and if the monitoring team has no way of applying retroactiv
  2. I think that would help, @Sarah Terry. The main issue I'm trying to avoid is this: we recently went through and removed users with no recorded activity. Some of them ended up being API users that were heavily used, but "Last Action" date from the users screen was blank and there was no activity in the audit log.
  3. Today, the audit log captures any changes that an API user makes, but doesn't record any activity if you are just making queries. It would be valuable to log all types of API calls to comprehensively monitor API user behavior. This could be done with one of the following: 1) A separate API-only audit log 2) Bundled with the existing audit log 3) The existing audit log could have an easy filter to hide API calls and reduce noise
  4. LogicMonitor, any updates on the possibility of getting this feature implemented?
  5. As we move towards a DevOps model, we increasingly have a need for small teams to have full admin access to the tools they use to manage their IT services. When it comes to LogicMonitor, this has proven difficult with the existing role permission model. DevOps pods would like to be able to manage their own datasources, alerts, and escalation chains but this isn't possible unless we give them broad access rights to those areas, which could cause significant harm to other groups of monitoring users. For example, an inexperienced DevOps user could inadvertently modify a datasource that applies to
  6. When a monitor malfunctions (e.g. service test fails because the monitored site HTML was updated) the uptime for that test will not reflect the site's actual uptime. We'd like to be able to apply retroactive SDT-like windows that would prevent an alert period from counting against a test's uptime. I thought this ability was already available by applying retroactive SDT's, but apparently this isn't actually working. Without this feature, a dashboard SLA widget might report a service/device being up 70%, but it was really up 90% while 20% of that time it had a faulty test/datasource. We sho
  7. Today, the system.displayname property for an AWS device is not automatically updated when the "Name" property in AWS is changed. It would make it easier to see which devices we are actually monitoring if the display names in LogicMonitor were synced with the current "Name" property in AWS.