ErnieC
Joined 8 years ago
User Profile
User Widgets
Contributions
- 3Views0likes0Comments
Include internal collector name in alerts
Currently, a service alert has the following limitation: ##CHECKPOINT##- the checkpoint associated with the alert (this value will be 'Overall' if the alert wastriggered based on the checks at multiple locations) There is no way to show the failing one, only the number of failures. It would be nice to have the collector (or multiple collectors)name included in the alert. Currently, you need to go to the service check and refer to a graph. Not helpful with email/texts I have posted something similar in the past about External Collectors, but internal ones would be useful -/topic/1510-include-external-collector-name-in-alert?do=embed" style="height:221px;max-width:502px;">0Views0likes0CommentsRe: Dynamic Tables (dashboard widget)
@Ali Holmesthat is a good start, although I was told the same thing last November by my account manager. It's been almost a year and no progress has been made and this is still being spec'd out? I alsokinda agree with @mnagel- there shouldn't be a problem just NaN'ing the "bad" cell in the table. Doing one is a good start, but let's not be content with just that. For what it's worth, you can kind of "ghetto" this up already with a line chart. The data and logic is already baked in, just displayed as a point on a graph over time, instead of the most recent datapoint.4Views0likes0CommentsInclude external collector name in alert
Currently, a service alert has the following limitation: ##CHECKPOINT##- the checkpoint associated with the alert (this value will be 'Overall' if the alert wastriggered based on the checks at multiple locations) There is no way to show the failing one, only the number of failures. It would be nice to have the collector (or multiple collectors)name included in the alert. Currently, you need to go to the service check and refer to a graph. Not helpful with email/texts2Views0likes0CommentsDynamic Tables (dashboard widget)
Currently, a table must have static columns and rows defined before the widget will display data. It would be great to be able to dynamically build a table's rows based on * To expand on this, it would be great for the table to have the option to excludeinstances with zero/no data from the list. For example, I would like a table that displays all MSMQ queue names and the number of messages in eachqueue - but not display anything if the current queue length = 022Views3likes13Comments