You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Two problems:
buffer_type tag in metrics is always reporting memory even if buffer start using disks on overflow
Some metrics with higher traffic goes to disks - as in problem 1 we don't see when reaching memory limit and start using disk because its reporting always memory buffer in internal metrics - but when reach disk this is growing and looks like not sending or not cleaned once sended from disks
When we look into one of the kpods we see that disk buffer is used and growing just like showed on graphs.
## non custom metrics comming from dd-agent - non DogstatsD
type: datadog_metrics
inputs:
- metrics_route._unmatched
# - datadog_agent
default_api_key: "SECRET[secrets.METRICS_EGRESS_DD_API_KEY]"
endpoint: "${DD_SITE}" # override for pvlink instead of public site option
buffer:
- type: memory
max_events: 50000
when_full: overflow
- type: disk
max_size: 15000000000 # close to 15GB - total 9GB+ with internal metrics and we have 10GB now on volume.
when_full: block
batch:
max_events: 5000
timeout_secs: 1
acknowledgements:
enabled: False
request:
concurrency: "adaptive"
Version
0.37
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered:
Thanks for this report @szibis . I'm not actually sure when the buffer files are deleted when events are processed. @tobz is this something you know off the top of your head?
A note for the community
Problem
Two problems:
When we look into one of the kpods we see that disk buffer is used and growing just like showed on graphs.
No additional info in logs.
Configuration
Version
0.37
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: