[Prometheus Remote Write] Update request size limits#16962
[Prometheus Remote Write] Update request size limits#16962
Conversation
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
| metrics_count: {{metrics_count}} | ||
| rate_counters: {{rate_counters}} | ||
| use_types: {{use_types}} | ||
| max_compressed_body_bytes: {{max_compressed_body_bytes}} |
There was a problem hiding this comment.
See beats relevant config options: https://github.com/elastic/beats/blob/main/metricbeat/module/prometheus/remote_write/config.go#L35C58-L35C80
| conditions: | ||
| kibana: | ||
| version: "^8.16.0 || ^9.0.0" | ||
| version: "^9.2.4 || ^9.3.1 || ^9.4.0" |
There was a problem hiding this comment.
There was a problem hiding this comment.
I don't think changing kibana version to this is a good idea.
Any future bugfixes will be skipped for 18.9, 9.0, 9.1, 9.3.0.
Can we instead the agent version requirment for this configuration int he documentation of the conig parameters ?
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
|
@elastic/obs-infraobs-integrations can I have a review here please? |
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
…ns into prometheus_body_bytes
|
@elastic/obs-infraobs-integrations kind reminder please |
| conditions: | ||
| kibana: | ||
| version: "^8.16.0 || ^9.0.0" | ||
| version: "^9.2.4 || ^9.3.1 || ^9.4.0" |
There was a problem hiding this comment.
^9.2.4 already includes ^9.3.1 and ^9.4.0, were you intending to set something like ~9.2.4 || ~9.3.1 || ^9.4.0?
There was a problem hiding this comment.
Let me clarify with an example: If someone tries 9.2.3 should not match.
And also if someone tries 9.3.0 should also not match. So I would like to include 9.2.4 but not 9.3.0
Is not this the correct approach?
There was a problem hiding this comment.
^ matches all the versions in the same major over the indicated version. ^9.2.4 is equal to ">= 9.2.4 AND < 10.0.0", so ^9.2.4 || ^9.3.1 || ^9.4.0 includes 9.3.0.
You need to use ~ to match only versions of the same minor, so ~9.2.4 || ~9.3.1 || ^9.4.0.
There was a problem hiding this comment.
@gizas : I still think this should not be done. As doing this we are actually removing any future support to versions like 8.19, 9.0, 9.1, 9.2 (lesser than 9.2.4), 9.3.0.
Can we instead update about this agent version dependency in the readme.
There was a problem hiding this comment.
for core integrations like prometheus we really want to retain support for 8.x customers.
There was a problem hiding this comment.
The reason for that was that the beats fix elastic/beats#48218 was not imported to 8.19 versions.
See above PR for relevant backports.
This relates to previous comment from Ishleen.
If you agree I can do:
^8.16.0 || ^9.2.4 || ^9.3.1 || ^9.4.0
and just document the limitations in README?
There was a problem hiding this comment.
^8.16.0 || ^9.2.4 || ^9.3.1 || ^9.4.0 is equivalent to ^8.16.0 || ^9.2.4, so the package will be available in 9.3.0.
You probably want ^8.16.0 || ~9.2.4 || ^9.3.1.
There was a problem hiding this comment.
Thank you @jsoriano ! @tommyers-elastic , @ishleenk17 do u agree to proceed with above versions and also document the fact that the existing variables will not work in 8.x ?
There was a problem hiding this comment.
@tommyers-elastic , @ishleenk17 I did the backport to 8.19. See elastic/beats#48918
So now "^8.19.3 || ~9.2.5 || ^9.3.1" is the final one.
Can I have another review please?
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Signed-off-by: Andreas Gkizas <andreas.gkizas@elastic.co>
…ns into prometheus_body_bytes
💚 Build Succeeded
History
|
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
|
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
Dont merge until ^9.2.4 || ^9.3.1 || ^9.4.0 are released
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
integrations/packages/prometheusand runelastic-package buildRelated issues
Screenshots