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

[APM] Remove the watcher integration and document the watcher error reporting #70324

Closed
nehaduggal opened this issue Jun 30, 2020 · 3 comments · Fixed by #71655
Closed

[APM] Remove the watcher integration and document the watcher error reporting #70324

nehaduggal opened this issue Jun 30, 2020 · 3 comments · Fixed by #71655
Assignees
Labels
Team:APM All issues that need APM UI Team support v7.9.0

Comments

@nehaduggal
Copy link

nehaduggal commented Jun 30, 2020

Documentation issue #70448

We currently offer two ways of setting up error rate alerts via watcher and via the new alerting UI in Kibana. In order to keep the alerting simple, we should get rid of the older watcher error rate integration and remove that dropdown from the APM App. We should document this removal in the UI and provide the recipe to create the watcher error in the documentation.

@formgeist @sqren

@nehaduggal nehaduggal added the Team:APM All issues that need APM UI Team support label Jun 30, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

@formgeist
Copy link
Contributor

We should document this removal in the UI and provide the recipe to create the watcher error in the documentation.

IMO it would be sufficient to announce it in the release notes and add it in the documentation, but perhaps that's what you mean?

@formgeist
Copy link
Contributor

I opened #70448 to handle the documentation side. We can move this into implementation in order to remove the Integrations option entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support v7.9.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants