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

[Custom threshold] Add new source fields in alert document #180707

Closed
Tracked by #183516
benakansara opened this issue Apr 12, 2024 · 5 comments
Closed
Tracked by #183516

[Custom threshold] Add new source fields in alert document #180707

benakansara opened this issue Apr 12, 2024 · 5 comments
Labels
Feature:Alerting Team:obs-ux-management Observability Management User Experience Team

Comments

@benakansara
Copy link
Contributor

benakansara commented Apr 12, 2024

We would like to add following fields at root level in "Custom threshold" alert document so they are available to query, search and identify signals (service.name, container.id, etc.) from the alert.

  • service.name
  • service.environment
  • transaction.type
  • transaction.name
  • error.grouping_key
  • error.grouping_name
  • host.name
  • host.hostname
  • container.id
  • host.id
  • kubernetes.pod.uid

Acceptance criteria

If group by fields include one or more of the above fields, they are available in alert document at root level.

@benakansara benakansara added Feature:Alerting Team:obs-ux-management Observability Management User Experience Team labels Apr 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@jasonrhodes
Copy link
Member

@tommyers-elastic can we chat about this?

@maryam-saeidi
Copy link
Member

maryam-saeidi commented Apr 25, 2024

@jasonrhodes Maybe it would be a good idea to also have a chat with the SRE team, for example, @elkargig. (Regarding the proposed list)

@jasonrhodes
Copy link
Member

@maryam-saeidi yes, for sure -- I believe @cnasikas has been in close contact with @elkargig and others in SRE as he's been trying to scope out this issue broadly, so it would be great for us to work closely with him as we prioritize this work.

@jasonrhodes
Copy link
Member

This is completed by #188241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Development

No branches or pull requests

4 participants