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.

Sign up for GitHub

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

Jump to bottom

[Monitoring] Introduce deprecation warning for shipping monitoring data to the production cluster #49591

Closed
cachedout opened this issue Nov 26, 2019 · 4 comments
Closed

[Monitoring] Introduce deprecation warning for shipping monitoring data to the production cluster #49591

cachedout opened this issue Nov 26, 2019 · 4 comments
Labels
:Data Management/Monitoring Team:Data Management Meta label for data/management team

Comments

@cachedout
Copy link
Contributor

cachedout commented Nov 26, 2019 •
edited by chrisronline
Loading

This issue is a request for Elasticsearch to add a deprecation log entry in 7.6 for users who are shipping monitoring data to the production cluster which urges them to switch to using Metricbeat monitoring in order to be prepared for 8.0.

If desired, the warning could link to instructions for doing so which are described here: https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html

cc: @jakelandis @elastic/stack-monitoring
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Monitoring)

@cachedout
Copy link
Contributor Author

@jakelandis Is this something you could add for us?

@jakelandis
Copy link
Contributor

@cachedout - I'm not sure we want to emit deprecation warnings until we ship Metricbeat with ES.

@cachedout cachedout mentioned this issue Dec 5, 2019
Closed
@chrisronline chrisronline changed the title [Monitoring] Introduce deprecation warning for internal collection [Monitoring] Introduce deprecation warning for shipping monitoring data to the production cluster Jan 13, 2020
@rjernst rjernst added the Team:Data Management Meta label for data/management team label May 4, 2020
@jakelandis
Copy link
Contributor

this issue has been resolved via #79499

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Data Management/Monitoring Team:Data Management Meta label for data/management team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cachedout @rjernst @jakelandis @elasticmachine