[8.19](backport #44493) [Metricbeat] [Prometheus] Add proper error handling for query dataset when the auth/ssl is misconfigured#44531
Merged
mykola-elastic merged 1 commit into8.19from May 29, 2025
Conversation
6 tasks
gizas
approved these changes
May 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
[Metricbeat] [Prometheus] Query dataset: make understandable error messages in case for http error codes
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
No impact
Author's Checklist
How to test this PR locally
My test environment:
Related issues
querydataset integrations#13751Screenshots & Logs
When running Metricbeat with wrong Prometheus' username and password the error message looks like that now:
and the debug message to the logs
When the protocol is HTTP but the Prometheus is configured to use HTTPS:
and the debug message to the logs:
Which is now the same behavior as of
collectorsubmoduleThis is an automatic backport of pull request #44493 done by [Mergify](https://mergify.com).