Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Show key string in monitor UI for per bucket monitor #1282

Closed
atammy-narmi opened this issue Oct 24, 2023 · 1 comment
Closed

[FEATURE] Show key string in monitor UI for per bucket monitor #1282

atammy-narmi opened this issue Oct 24, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@atammy-narmi
Copy link

atammy-narmi commented Oct 24, 2023

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.
alerts-photo

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.

@praveensameneni
Copy link
Member

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}}

{{/ctx.alerts}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants