Question about monitoring multiple instances about process-exporter HOT 2 CLOSED

First, sorry for the very late reply.

I fixed the broken example in the help, thanks for pointing it out.

Now, as to your question, I'm not sure exactly what you intend and you haven't explained how it's failing, but I think what you proposed looks reasonable, although you don't need the .* at the beginning or end of your cmdline regexp.

I don't have any experience with ES, but it's entirely possible that it spawns other processes that also contain -cp /opt/atlassian/stash/4.9.1/elasticsearch/lib/elasticsearch-2.3.1.jar on the command line. As such, you might be better off with something like

cmdline:
- -cp\s+/opt/atlassian/stash/4\.9\.1/elasticsearch/lib/elasticsearch-2\.3\.1\.jar
- org\.elasticsearch\.bootstrap\.Elasticsearch\s+start

which will only match processes that have both the "-cp /opt/atlassian/stash/4.9.1/elasticsearch/lib/elasticsearch-2.3.1.jar" AND "org.elasticsearch.bootstrap.Elasticsearch start".

I'd probably replace the version strings with wildcards too so that if you upgrade you don't have to adapt the regexes, e.g.

- -cp\s+/opt/atlassian/stash/\d+\.\d+\.\d+/elasticsearch/lib/elasticsearch-\d+\.\d+\.\d+\.jar

from process-exporter.

Closing as I think the question has been answered. Feel free to re-open if that's not the case.

from process-exporter.