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

Should we have universal connector context variables? #112080

Open
gmmorris opened this issue Sep 14, 2021 · 2 comments
Open

Should we have universal connector context variables? #112080

gmmorris opened this issue Sep 14, 2021 · 2 comments
Labels
discuss estimate:small Small Estimated Level of Effort Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gmmorris
Copy link
Contributor

Relates to #112079

When testing connectors there are no context variables available.
Adding some universal context variables (that are always available) would enable customers to test how they interact with context variables prior to setting up a rule.

This is not an alternative to the ability to test them on a rule (which would mean we can add context-dependent dummy variables) but it could help customers when testing the connectors from Stack Management.

@gmmorris gmmorris added discuss Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX estimate:small Small Estimated Level of Effort labels Sep 14, 2021
@elasticmachine
Copy link
Contributor

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

@pmuellr
Copy link
Member

pmuellr commented Sep 14, 2021

I did a quick look when looking at the support case for this. Seems like the only existing top-level mustache variables that would make sense would be date and kibanaBaseUrl. The rest are alerting-related, so seem a bit out of scope. Turns out for the support case, the user was looking to use the date variable ...

@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
discuss estimate:small Small Estimated Level of Effort Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

4 participants