q000p

in the manual wrote: > To avoid using unbounded memory, metrics will be garbage collected **five minutes** after they are last pushed to. This is configurable with the --graphite.sample-expiry flag....

This part of docker stack .yml file: ` graphite-exporter: image: prom/graphite-exporter:v0.13.1 ports: - "9108:9108" - "9109:9109" volumes: - graphite-configs:/tmp:ro command: - '--graphite.mapping-config=/tmp/graphite_mapping.conf' ` 

On screenshot you can see time when straight line started (11h) and ended (14h). 14-11=3h

Now I add line ` - '--graphite.sample-expiry=1m' ` But haven`t result. What reason?

If I open http://192.168.59.20:9108/metrics I see ``` # HELP mpa1000_cpu_usage Graphite metric mpa1000_cpu_usage # TYPE mpa1000_cpu_usage gauge mpa1000_cpu_usage{ip="192_168_223_40",job="mpa1000log"} 25.510204315186 # HELP mpa1000_temperature Graphite metric mpa1000_temperature # TYPE mpa1000_temperature gauge mpa1000_temperature{ip="192_168_223_40",job="mpa1000log"}...

Turned off the source. After 10 minutes the same ``` graphite_sample_expiry_seconds 300 # HELP graphite_tag_parse_failures Total count of samples with invalid tags # TYPE graphite_tag_parse_failures counter graphite_tag_parse_failures 0 # HELP...

Yes, I turned off 192.168.223.40 ``` { "request": { "url": "api/ds/query", "method": "POST", "data": { "queries": [ { "datasource": { "type": "prometheus", "uid": "aJMidLhVk" }, "editorMode": "builder", "expr": "mpa1000_video", "legendFormat":...

I use it on mikrotik but I have a problem. Container cannot start after mikrotik reboot. I used adguardhome:latest tag with v0.107.69 Log is attached. ` 2025-11-21 11:00:01 adguardhome:latest internal/poll.(*FD).Accept(0x40000ea280)...