-
Notifications
You must be signed in to change notification settings - Fork 100
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
If source doesn't send metrics it is not removed from list #217
Comments
This is already supported:
If this is configured but does not work, please re-open this issue with the following information:
|
in the manual wrote:
|
That's odd – we don't set it there at all. How are you running the image? Can you share the whole command you use? |
How did you determine that it is 3 hours? |
On screenshot you can see time when straight line started (11h) and ended (14h). 14-11=3h |
Now I add line |
1 minute may be too little, depending on how often you send samples. What happens when you set it to 5m? Can you get the raw samples for the last few hours from Prometheus and see what it really knows? Something like Also, please look at the exporter's metric page, and see what metrics are there when. |
What is the query in that dashboard? |
If I open http://192.168.59.20:9108/metrics
|
so that is only the current one now. Applying your changes restarts the exporter, which always clears everything. You will need something to appear and disappear to see any effects. |
Turned off the source.
|
t send metrics it don
t removed from listt send metrics it doesn
t removed from list
t send metrics it doesn
t removed from list
When you say you "turned off the source", did that include 192.168.223.40? What is the query used in the Grafana dashboard? |
Yes, I turned off 192.168.223.40
|
Im having this very issue in version 0.15.0 running in docker |
If you turn off the source exporter remember last value and will be send it.
On screenshot it 223_40 and 223_41
Could you remove source after it don`t send values?
The text was updated successfully, but these errors were encountered: