add setting PROMETHEUS_TOTAL_BYTES_BUCKETS for metric body size #490
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.
Hi
At work, I encountered a problem where our service has a release limitation due to the large number of buckets in some metrics. This limitation is due to the fact that a large number of buckets puts a heavy load on Prometheus.
More specifically, django_http_requests_body_total_bytes and django_http_responses_body_total_bytes
This is despite the fact that starting with le=2^17 in django_http_requests_body_total_bytes_bucket and le=2^24 in django_http_responses_body_total_bytes_bucket, there is no difference.
In fact, the difference between le=2^24 and le=2^17 in django_http_requests_body_total_bytes_bucket is 16 for 320k requests.
I propose enabling custom bucket sizes.