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

Can one instance of apache_exporter monitor two or more apache instances? #37

Closed
ping2nomula opened this issue Jan 12, 2018 · 5 comments

Comments

@ping2nomula
Copy link

We have two or more apache instances on the same host and wants to monitor it using apache_exporter. Do i need to have more instances of apache_exporter running or one is enough?

@Lusitaniae
Copy link
Owner

Lusitaniae commented Jan 13, 2018

You need multiple instances.
Prometheus philosophy is to have one exporter process for each thing being monitored.

@mmranger
Copy link

mmranger commented Mar 3, 2020

You need multiple instances.
Prometheus philosophy is to have one exporter process for each thing being monitored.

Would multiple vhosts/sites be considered multiple 'instances'? Also doesn't your phpfpm_exporter handle multiple instances via --phpfpm.socket-paths?

Example: Server running 3 vhosts, and two versions of php. With this setup I use one phpfpm_exporter with the two php versions. But I need to setup 3 apache_exporters(0-2) to accommodate each vhost/site.

Of course I don't know golang/apache/php well anyway, so if this is an annoying (my example setup is flawed for instance) question feel free to ignore.

Thanks.

@Lusitaniae
Copy link
Owner

Lusitaniae commented Mar 3, 2020 via email

@leonk
Copy link

leonk commented Aug 23, 2022

Don’t suppose anyone has an example of how to set this up with kubernetes?

I’m able to create two separate services in k8ns, but not sure how I could get each individual pod running the apache exporter to connect directly to a pod running Apache.

@Lusitaniae
Copy link
Owner

Lusitaniae commented Aug 23, 2022 via email

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

4 participants