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
Is your feature request related to a problem?
When creating a per bucket monitor and an alert getting triggered, the monitor only has the trigger name in the monitor UI. This makes it impossible to distinguish alerts by what bucket they are referring to. It would be helpful to have a distinguishing feature per bucket in the UI.
Like for the following alert where it monitors VPN healths, I got alerts for 10 VPN health checks which failed and while I can acknowledge them individually, I can't tell which one I am acknowledging.
What solution would you like?
Add the per bucket string in the UI for a per bucket monitor.
What alternatives have you considered?
Any other distinguishing feature for the buckets would work as well.
The text was updated successfully, but these errors were encountered:
We introduced the above enhancement in 2.13
PR: #1450
Here's an example of how to show sample documents
{{#ctx.alerts}}
Sample documents:
{{#sample_documents}}
Index: {{_index}}
Document ID: {{_id}}
Order date: {{_source.order_date}}
Order ID: {{_source.order_id}}
Clothing category: {{_source.category}}
-----------------
{{/sample_documents}}
Is your feature request related to a problem?
When creating a per bucket monitor and an alert getting triggered, the monitor only has the trigger name in the monitor UI. This makes it impossible to distinguish alerts by what bucket they are referring to. It would be helpful to have a distinguishing feature per bucket in the UI.
Like for the following alert where it monitors VPN healths, I got alerts for 10 VPN health checks which failed and while I can acknowledge them individually, I can't tell which one I am acknowledging.
What solution would you like?
Add the per bucket string in the UI for a per bucket monitor.
What alternatives have you considered?
Any other distinguishing feature for the buckets would work as well.
The text was updated successfully, but these errors were encountered: