Mosh

Members
  • Content Count

    509
  • Joined

  • Last visited

  • Days Won

    78

Community Reputation

104 Excellent

2 Followers

About Mosh

  • Rank
    Community All Star

Recent Profile Visitors

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

  1. Mosh

    Alert 'pinning'

    We would like to have the ability to "pin" an alert. Use case, an alert is raised for file system utilization, but it's right on the threshold and is fluctuating just enough for the alert to clear the next day, but then comes back the day after that, or a couple of days later. This results in fresh tickets being opened each time. Ops would like to be able to ping the alert, because they know they will need to expand the file system but it might take a week or three to arrange an outage on the business service, and get the change request approved (enterprise environment). Pinning the alert would mean the alert remain in place and does not clear until manually unpinned. Even better would be if LogicMonitor could intelligently detect this kind of condition and auto pin. #AIOps
  2. Mosh

    Windows Event Logs - Applications and Services

    I have the same issue. I need to monitor Windows Task Scheduler events. Can anyone from LogicMonitor please respond and suggest the best way to achieve this.
  3. Mosh

    Restore ability to view Widget ID

    Hi @Will Johnson - LM Thanks for the workaround. Yes please, it's useful to be able to find the widget ID easily and quickly.
  4. We seem to have lost the ability to view the ID of a dashboard widget. Previously I was able to see this somewhere in the widget configuration view. Please restore the widget ID back into the widget configuration view. We use this to find the ID of a widget to use with the REST APIs.
  5. Mosh

    Allow Logarithmic scaling of graphs

    @madan Using this REST API endpoint: /dashboard/widgets/{widgetID}/data
  6. Please make it so that when configuring a website monitor that has multiple Steps, we can set it so that it only alerts if all steps fail. In other words, if any one of the steps passes, then everything is still okay. For example, I have a primary URL for an API endpoint, and a secondary URL. As long as either is available I don't need an alert. Only if both steps fail, then I want an alert.
  7. Please make the "Are you sure?" an option that can be disabled in Settings. For us non-MSP enterprise customers that extra mouse click would be a frustration. I like the idea of locking groups as this means we can turn off the confirmation prompt, and know that important service groups are locked from accidental drag and drop.
  8. Mosh

    Allow NESTED Dashboards

    I too would like to be able to configure the NOC widget so that clicking on the a NOC widget item takes us to another dashboard rather than the resource.
  9. We very frequently need to jump between a monitored resource and the collector resource that is doing the monitoring. Please make the system.collectordesc on the Info page of a resource into a hyperlink to the collector resource. This would turn multiple keystrokes/clicks into a single click operation to navigate from a resource to the resource's collector.
  10. For JDBC datasources, please create a token that would enable us to include the JDBC driver exception message in the alert for Query Status data point alerts, the ones that are based on: Query status - 1=ok, 2=credential invalid, 3=connection string invalid, 4=connection rejected, 5=driver not supported, 6=connection failure, 7=query failure This would greatly help us to achieve faster time to resolution of incidents when the exception is code of type 6 and 7.
  11. At the moment we lose our alert notes if an alert is revoked. Please make so that alert notes are retained so we can view them by viewing cleared alerts. The "alert is revoked" should be stored in a separate property of the alert.
  12. Mosh

    Dependencies or Parent/Child Relationships

    I'm interested too please.
  13. We've had instances where Ops folks (usually newbies) have set an SDT with duration much longer than they intended. Please add an option to enable us to limit the maximum duration for SDTs. For example, we'd like to limit SDTs to be no greater than 90 days from timenow. It would suffice for us if this was a system wide setting.
  14. I'm not sure if this is a bug or a feature enhancement. An overview graph in the resource view includes data for instances of an data source that previously existed (which is super useful for A/B comparison!). However, the the "Add to dashboard" option is used to add the graph to a dashboard, the graph only shows the current instance's data. Please make it so that when the graph is added to a dashboard, that the dashboard copy also shows the data for the previous data source instances, as this is what our users expect when they do this.
  15. @Michael Fisher Our preference would be that only admins get major new features. Reason being we may grant some of our functions to manage things, but use of major new features is something is release into our environment through a managed process, as we undertake analysis to understand behavioral impact of new features. If people receive a new feature it's because we want them to use it a certain way, rather than leave it to them to go off and do things might not be optimal from a operational process perspective (lean principles, six sigma, etc.) I love agility, but efficient agility Thanks.