Mosh

Members
  • Content Count

    555
  • Joined

  • Last visited

  • Days Won

    83

Everything posted by Mosh

  1. @madan Using this REST API endpoint: /dashboard/widgets/{widgetID}/data
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. @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.
  11. For info, looking through the tickets we had, some users actually thought Mapping was something else; they thought it was to do with "making maps" - as in customized Google maps type views, hence their excitement. So that's interesting for us internally as it would seem people are not aware of the map widget!
  12. HI @Michael Fisher It's okay, it's my own fault! I did some further digging because I too was puzzled how they could see it. Turns out they couldn't see it, which is what the tickets were actually about. Traced it down to one user had admin role from ages ago (because it was the only way to work around a bug we encountered to do with the Reports view). That user saw Mapping, got excited and told everyone else! Phew, panic over.
  13. Please, please, please DO NOT enable by default major new features for non-admins. We've just had Mapping appear for every user with no warning; resulting in them raising tickets, which is costly for us using an outsourced service desk! We only give our users features that we want them to use. What's more I've just had to go through every user record to uncheck Mapping - not helped by the fact that the Users views returns to the first page of results every time! It's taken me an hour almost. @Sarah Terry @Ali Holmes
  14. At the moment when a datasource is disabled, the DS object can still have sub-objects in the resource tree (under the disabled section). These sub-objects still show up in the resource tree search results. This is very confusing for our users as they expect not to find them (and nor do we want them to see them). Please make it so that sub-objects of disabled datasources are excluded from resource tree searches. (Ideally I would suggest making this a toggle option in Settings in case some folks want the opposite behavior.)
  15. Just thought of this, you could make the "$" prompt of the debug console the name of the collector (as defined in the Collectors page).
  16. Also need to preserve the subject and body of customized notifications for data source's datapoints. Though I would much prefer to be able to define customis notifications templates separately and reference the template in the data point config. This would minimize the maintenace effort for customised notifications.
  17. Please implement more granular permissions for SDT function. We would like to be able to grant permission to apply SDT to data sources elements, but NOT on the resource itself. We often encounter situations where by accident or carelessness our staff apply SDT to a resource instead of the data source element.
  18. Thanks @Michael Fisher If the alert suppression is part of the core platform that is good news.
  19. Thanks @Chris Sternberg Will the topology module be a licensed module or included as part of a forthcoming update?
  20. Yes! Very frustrating to have to page through all the alert sources in the tuning view.
  21. Hi @Chris Sternberg We organise each countries network CIs (configuration items) into groups by firewalls, routers, switches and wireless (see attached image). What we need to be able to do is somehow say that if any CI under the Routers group and subgroups is down (ping loss and host status), then alerts should be suppressed for the Firewalls, Switches and Wireless groups and sub-groups. Will what you are proposing enable us to do this?
  22. @Linus Cool! My preference would be that clicking Alert icon should only clear severity filters, and leave any other filters intact. Of course, you could always add a double-click action to the Alert icon that clears all filters and resets the view.
  23. Filtering by alert severity requires more than one mouse click operation currently. It would be much quicker if we could simply click the alert severity count in the left nav bar and the alert list would be filtered by the severity clicked on. Clicking the main Alert icon item could be used to remove severity filter.