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

Add alerts/watchers as assets in packages #484

Closed
ChrsMark opened this issue Feb 28, 2023 · 4 comments
Closed

Add alerts/watchers as assets in packages #484

ChrsMark opened this issue Feb 28, 2023 · 4 comments
Labels
discuss Issue needs discussion Team:Ecosystem Label for the Packages Ecosystem team

Comments

@ChrsMark
Copy link
Member

At the moment we don't support alerts and watchers to be part of a package.
At elastic/integrations#4997 we explore how the alerting feature can enhance our Kubernetes solution.
After having the first bunch of alerts/watchers we decided to include them in the docs' section for now with elastic/integrations#5364.

The purpose of this issue is to propose to provide the option for alerts/watchers to be installed when installing the package. These means we should add them to their own place in the package-spec, and we should have a follow-up task in Kibana to install them when available.

@ChrsMark ChrsMark added the discuss Issue needs discussion label Feb 28, 2023
@jsoriano jsoriano added the Team:Ecosystem Label for the Packages Ecosystem team label Feb 28, 2023
@jsoriano
Copy link
Member

jsoriano commented Mar 1, 2023

@ChrsMark what would be needed to store in the packages, only the watcher definition? Or would some additional setting or identifier be needed too?

@ChrsMark
Copy link
Member Author

@jsoriano based on what we have so far, watcher's definitions would be the only thing to be stored. I cannot think of anything else what would need to be stored 🤔

@ruflin
Copy link
Member

ruflin commented Jun 1, 2023

Instead of adding support for watcher, we should instead add support for alerts and slo.

@jsoriano
Copy link
Member

Closing as duplicate of #121, let's keep discussions about this there.

@jsoriano jsoriano closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issue needs discussion Team:Ecosystem Label for the Packages Ecosystem team
Projects
None yet
Development

No branches or pull requests

3 participants