Uptime graph about process-exporter HOT 3 OPEN

I'm confused: how would doing the calculation in the app instead of in promql help with the graphing?

Personally I'm only ever interested in the uptime to know if the app was restarted, which you can get with changes(namedprocess_namegroup_oldest_start_time_seconds[interval]).

from process-exporter.

At the moment, namedprocess_namegroup_oldest_start_time_seconds would have the following data points (using very simplified examples):

If I graph that using time()-namedprocess_namegroup_oldest_start_time_seconds, I'd get the following points in my graph, depending on when I viewed it (since time() is "now, when the graph is shown"):

However, if the process_exporter information included an actual "uptime" for the process, I'd get values that were based on how long the process was running when the scrape took place, as so:

This would be very easy to graph, and would show a steadily rising line as processes ran, which then reset back to 0 when they were restarted.

If you can think of any other way to display this information, I'd be happy to do it in promql instead - I just can't figure out a way. I think I want scrape timestamp - start_time_seconds, but I have no idea how to get that value.

Alternatively, if you've got a good way of showing how long processes have been running (not just how many time's they've restarted in a particular interval), I'll use that instead.

from process-exporter.

I'm currently running into the same issue - I'm trying to replace some old scripts that fed data into graphite with the process-exporter. The purpose is to show the runtime of several cronjobs, giving an indication how long each run takes and if any cronjobs are running abnormaly long. The result is a graph containing a sawtooth pattern.

So far I have not managed to formulate a promql query that will give me this result, a separate uptime gauge would be very useful here.

@Rocketeer007 have you found any solution for this in the meantime?

from process-exporter.