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

How to pass High CPU Process Name in Kibana Alert Action #70174

Closed
Ranjan-Gupta01 opened this issue Jun 29, 2020 · 6 comments
Closed

How to pass High CPU Process Name in Kibana Alert Action #70174

Ranjan-Gupta01 opened this issue Jun 29, 2020 · 6 comments
Labels
💝community Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed

Comments

@Ranjan-Gupta01
Copy link

Hey Team,

As part of preventive monitoring through Kibana, we triggered an alert and used action WebHook. We were able to send Server Name, which triggered the alert, in the Body. We need to pass the process name as well to take appropriate action. With limited variables available, we are not sure which variable/object can help us sending the process name to Web Service.

May you please guide us with the process name in Kibana action?

Thanks, in advance for your help.

@azasypkin azasypkin added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 29, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@azasypkin
Copy link
Member

Hi @Ranjan-Gupta01 ,

The GitHub issues are intended for bug reports, enhancement requests and etc. The question you have fits better for our Discuss forum, would you mind posting questions like this there instead in the future? There much more users like you that can help and probably already solved the problem you have.

But as an exception, since you created it already, let's see if Alerting Services team can give you a hint.

@pmuellr
Copy link
Member

pmuellr commented Jun 30, 2020

What alert are you using? The index threshold alert is very generic, and doesn't provide access to data in the documents that's not used in the threshold calculation. The other more specialized alert types provide additional, specialized data, so we'd need to know which one you're using - guessing it's the metric threshold alert.

There's a similar issue open here - issue #69611 - "Expand the context available within Kibana Alerting" - perhaps we should move the request into that one ...

@Ranjan-Gupta01
Copy link
Author

Yes, it is for Metric Threshold alert type. And it is very much similar to #69611. We want to expand the context so that it can return other results while configuring the actions.

@pmuellr
Copy link
Member

pmuellr commented Jul 2, 2020

@Ranjan-Gupta01 do you want to close this one and add your requirement to the referenced issue #69611 ?

@Ranjan-Gupta01
Copy link
Author

Thanks, we can close this one and please add the requirement to the other issue #69611 . Thanks again for the help.

@pmuellr pmuellr closed this as completed Jul 3, 2020
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💝community Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed
Projects
None yet
Development

No branches or pull requests

6 participants