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

Only log error (don't also index it) if xpack is enabled. #12353

Merged
merged 2 commits into from
May 31, 2019

Conversation

ycombinator
Copy link
Contributor

When xpack.enabled: true is set on a stack module, the expectation is that the user won't see any metricbeat-* indices. Instead users expect to see .monitoring-* indices.

However, metricbeat indexes errors into metricbeat-* indices. So in an error situation when xpack.enabled: true is set, we don't want to index errors but just log them. That's what this PR fixes for the kibana/stats metricset.

Equivalent of #12265 but for 7.1 (see #12265 (comment) for rationale).

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring

@ycombinator ycombinator force-pushed the mb-kb-only-log-error-xp-71 branch from 52d471a to c3024eb Compare May 31, 2019 12:55
@ycombinator ycombinator merged commit 7f0ac09 into elastic:7.1 May 31, 2019
ycombinator added a commit that referenced this pull request Jun 3, 2019
…) (#12379)

* Only log error (don't also index it) if xpack is enabled.

* Adding CHANGELOG entry
@ycombinator ycombinator deleted the mb-kb-only-log-error-xp-71 branch December 25, 2019 11:18
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
)

* Only log error (don't also index it) if xpack is enabled.

* Adding CHANGELOG entry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants