Skip to content
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

namedprocess_namegroup_num_procs doesn't refresh when the process is up again #305

Open
shakenfr opened this issue Jul 3, 2024 · 1 comment

Comments

@shakenfr
Copy link

shakenfr commented Jul 3, 2024

Hello,

I have for exemple this promql code in prometheus alertmanager

(namedprocess_namegroup_num_procs{job='exporter-sd-process-exporter',groupname="kube-scheduler"}) == 1

when my process is lost or kill, it gives a value to 0 and alert (it's normal)

when the process is up again, the value remains 0 instead of 1 and the alarm remains until I restart process_explorer. ( not normal)

Is is possible that the process explorer refreshs without restart it ?

best
bruno

@blissend
Copy link

blissend commented Jul 8, 2024

Exactly what I'm trying to figure out. Doesn't look like process-exporter has a builtin way to rescan the /proc

EDIT: I stand corrected...

-recheck (default:false) means that on each scrape the process names are re-evaluated. This is disabled by default as an optimization, but since processes can choose to change their names, this may result in a process falling into the wrong group if we happen to see it for the first time before it's assumed its proper name. You can use -recheck-with-time-limit to enable this feature only for a specific duration after process starts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants