-
Notifications
You must be signed in to change notification settings - Fork 146
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
Comments
You need multiple instances. |
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. |
Apache can serve multiple vhosts from the same process.
Therefore you'll only need a single exporter.
Phpfpm exporter does *not follow the convention*, because you can create
multiple fpm pools and need to monitor each one individually, and the
exporter will monitor all from one instance (against convention)
If you’re running different Apache instances, because you may want to
segregate stats per vhost, then you’ll need different exporters for each
instance
Also, both exporters were originally written by other people, I've only added small things or review Pull Requests. Not intending to release incompatible changes to follow the convention at this point.
Hope it’s clear
…On Tue, 3 Mar 2020 at 16:16, Mike McQueen ***@***.***> wrote:
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.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#37?email_source=notifications&email_token=AAAOHVJSHPVEPQXABVBLGFLRFUUOZA5CNFSM4ELTQTZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENUD43I#issuecomment-594034285>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOHVKSJ3UWZOT2FYCVUTTRFUUOZANCNFSM4ELTQTZA>
.
|
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. |
Typically you use a "sidecar container pattern" approach
So each Apache container will have an apache exporter sidecar container
Maybe this article can guide you
https://medium.com/bb-tutorials-and-thoughts/kubernetes-learn-sidecar-container-pattern-6d8c21f873d
…On Wed, Aug 24, 2022 at 12:09 AM leonk ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOHVJHESJ46I6AIULDIFTV2UAWHANCNFSM4ELTQTZA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
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?
The text was updated successfully, but these errors were encountered: