You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current page is limited in that only generic VisLayer information is passed as input to the View Events flyout. Ideally, we want to allow plugins to inject more custom logic to enhance the information shown. This can include:
showing resource state (anomaly detectors in Running state, alerting monitors in Enabled state, etc.)
showing more resource information (when last updated, event count over periods of time, more config information)
custom aggregations in tooltips (a scale of anomaly grade & confidence, partitioning alerts based on severity)
custom rendering of event charts (different colors based on event details, such as anomaly grade or alert severity)
custom rendering of other chart types (e.g., line charts for forecasting, or other event types in the future, etc.)
More exploration will be needed in how we want to interface this injected plugin logic (registering logic somewhere?), and the balance of control between core Dashboards and plugins.
UPDATE: more info/proposed ideas in a duplicate issue #4180 . Pasting content here:
Currently, the View Events flyout is specific to PointInTimeEventsVisLayers. The way the flyout is laid out requires tight integration with the base visualization, and the sub-charts below showing each of the VisLayer events. Because of this tight integration, the implementation lives in VisAugmenter plugin in OSD, in order to keep things consistent, such that any plugins that emit events on top of a particular visualization is shown correctly and lined up such that the correlation shown within the flyout looks correct. This also gives us the benefit of all plugins that emit these events, will be organized and shown in a consistent manner for all plugins.
For integrations with future plugins and other potential VisLayer types that may be introduced, we may want to have VisAugmenter have less control over the rendering, and instead allow plugins themselves to control how a deep-dive into the VisLayer may look. For example, for looking at details of forecasting results on top of a visualization, we may want to just show an empty panel at the VisAugmenter level, and allow the plugin responsible for producing the forecasted results, show how they may want to provide more details or a more thorough breakdown of those results.
This can be done using UIActions, such that VisAugmenter could use triggers such that plugins could have actions associated with them to perform different actions (e.g., trigger with context including the visualization to allow the plugin to re-render the visualization along with a detailed breakdown of the forecasted data).
The text was updated successfully, but these errors were encountered:
ohltyler
changed the title
[Feature Anywhere] Support more custom plugin functionality in View Events flyout
[Feature Anywhere] [P1] Support more custom plugin functionality in View Events flyout
Feb 21, 2023
ohltyler
changed the title
[Feature Anywhere] [P1] Support more custom plugin functionality in View Events flyout
[Feature Anywhere] [Future] Support more custom plugin functionality in View Events flyout
Feb 21, 2023
ohltyler
changed the title
[Feature Anywhere] [Future] Support more custom plugin functionality in View Events flyout
[Feature Anywhere] [Enhancement] Support more custom plugin functionality in View Events flyout
Feb 21, 2023
The current page is limited in that only generic
VisLayer
information is passed as input to the View Events flyout. Ideally, we want to allow plugins to inject more custom logic to enhance the information shown. This can include:Running
state, alerting monitors inEnabled
state, etc.)More exploration will be needed in how we want to interface this injected plugin logic (registering logic somewhere?), and the balance of control between core Dashboards and plugins.
UPDATE: more info/proposed ideas in a duplicate issue #4180 . Pasting content here:
Currently, the View Events flyout is specific to
PointInTimeEventsVisLayer
s. The way the flyout is laid out requires tight integration with the base visualization, and the sub-charts below showing each of theVisLayer
events. Because of this tight integration, the implementation lives inVisAugmenter
plugin in OSD, in order to keep things consistent, such that any plugins that emit events on top of a particular visualization is shown correctly and lined up such that the correlation shown within the flyout looks correct. This also gives us the benefit of all plugins that emit these events, will be organized and shown in a consistent manner for all plugins.For integrations with future plugins and other potential
VisLayer
types that may be introduced, we may want to haveVisAugmenter
have less control over the rendering, and instead allow plugins themselves to control how a deep-dive into theVisLayer
may look. For example, for looking at details of forecasting results on top of a visualization, we may want to just show an empty panel at theVisAugmenter
level, and allow the plugin responsible for producing the forecasted results, show how they may want to provide more details or a more thorough breakdown of those results.This can be done using
UIActions,
such thatVisAugmenter
could use triggers such that plugins could have actions associated with them to perform different actions (e.g., trigger with context including the visualization to allow the plugin to re-render the visualization along with a detailed breakdown of the forecasted data).The text was updated successfully, but these errors were encountered: