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

Trying to edit the action part to a trigger. #62379

Open
wxyvk opened this issue Apr 2, 2020 · 4 comments
Open

Trying to edit the action part to a trigger. #62379

wxyvk opened this issue Apr 2, 2020 · 4 comments
Labels
enhancement New value added to drive a business result Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@wxyvk
Copy link

wxyvk commented Apr 2, 2020

Describe the feature:

Hello , I am trying to edit the action part of a trigger . In the message box which goes like an alert to the recepients; currently these fields are available ctx.timestamp start: ; ctx.timestamp end: , ctx.severity, ctx.trigger name.
Describe a specific use case for the feature:
Do we have the flexibility to add fields of an index pattern that I currently have. More specifically every field that I find under discover button, would it be possible to extract it through ctx?

@wxyvk wxyvk changed the title trying edit the action part to a trigger. Trying to edit the action part to a trigger. Apr 2, 2020
@liza-mae liza-mae added Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Apr 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@cjcenizal cjcenizal added enhancement New value added to drive a business result Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 12, 2020
@elasticmachine
Copy link
Contributor

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

@pmuellr
Copy link
Member

pmuellr commented May 14, 2020

Given the name of the context variables, this seems like it must be related to Watcher vs Kibana Alerting.

@cjcenizal
Copy link
Contributor

@pmuellr Sorry, I should give context for why I added the Alerting Services label. Per discussion with @bmcconaghy, the ES UI team will add this label to any Watcher issues for features or functionality which seem relevant to Kibana Alerting (i.e. something y'all may want to build).

@gmmorris gmmorris removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

6 participants