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
fix inconsistent behaviors with prometheus when scraping #5153
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #5153 +/- ##
=======================================
Coverage 60.19% 60.20%
=======================================
Files 398 398
Lines 74120 74200 +80
=======================================
+ Hits 44618 44673 +55
- Misses 26991 27019 +28
+ Partials 2511 2508 -3
☔ View full report in Codecov by Sentry. |
b16cbbd
to
f680eb9
Compare
f93f49e
to
f9f7590
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
451bb24
to
b1cd497
Compare
1. address #4959. skip job with wrong syntax in `scrape_configs` with error logs instead of exiting; 2. show error messages on vmagent /targets ui if there are wrong auth configs in `scrape_configs`, previously will print error logs and do scrape without auth header; 3. don't send requests if there are wrong auth configs in: 1. vmagent remoteWrite; 2. vmalert datasource/remoteRead/remoteWrite/notifier.
b1cd497
to
179a3d1
Compare
@Haleygo , thanks for the pull request! It looks great overall. I noticed a few issues while reviewing the pull request - some of these issues existed before this pull request. I'd recommend taking a look at the follow-up commit, which addresses these issues - d5a599b . If you notice some issues in this commit, then feel free sending follow-up pull requests on top of this commit! |
* fix inconsistent behaviors with prometheus when scraping 1. address #4959. skip job with wrong syntax in `scrape_configs` with error logs instead of exiting; 2. show error messages on vmagent /targets ui if there are wrong auth configs in `scrape_configs`, previously will print error logs and do scrape without auth header; 3. don't send requests if there are wrong auth configs in: 1. vmagent remoteWrite; 2. vmalert datasource/remoteRead/remoteWrite/notifier. * add changelogs * address review comments * fix ut
…rics#5153) * fix inconsistent behaviors with prometheus when scraping 1. address VictoriaMetrics#4959. skip job with wrong syntax in `scrape_configs` with error logs instead of exiting; 2. show error messages on vmagent /targets ui if there are wrong auth configs in `scrape_configs`, previously will print error logs and do scrape without auth header; 3. don't send requests if there are wrong auth configs in: 1. vmagent remoteWrite; 2. vmalert datasource/remoteRead/remoteWrite/notifier. * add changelogs * address review comments * fix ut
FYI, this pull request has been included in v1.95.0 release. |
scrape_configs
with error logs instead of exiting;scrape_configs
, previously will print error logs and do scrape without auth header;