-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support monitoring over SSH #1
Comments
Thanks Chet, very appreciated. For our purpose maybe just having the Monitoring Template via ssh could be ok, we could leave out modeling and just get data point if it is possible |
Can i second this. Having to open and secure 5432 is a real annoyance, particually when an ssh service account infrastructure already exists. |
Just chiming in to see if this has had any progress ? I'm still really wanting to use this zenpack, but there's no way i'm opening port 5432 up across my estate. |
@robertpearce: No, I don't think anyone is currently working on it. I wouldn't advocate opening 5432 to everyone either. I'd surely rather only open it to servers that needed access such as the Zenoss collector. |
no, but my issue is the db's i'm monitoring are offsite, over several vpn links and the 4-5 firewalls that entails managed by 3 different companies, so opening 5432 even just to the monitoring host is a pain. |
@robertpearce: I feel your pain. This isn't going to be a trivial thing to add. Right now the collection uses a direct connection to PostgreSQL using a client library. Going over SSH would probably mean invoking the queries through the psql command line utility. It would end up being an entirely new modeling plugin and set of monitoring templates. At least the model could be reused. |
yeah, it's ok. I came to a similar conclusion just a minute ago when looking at the source code. |
Alexander Fortin [email protected] requested support for monitoring over SSH to the PostgreSQL server instead of the native PostgreSQL protocol. This would be better for situations where you don't want to open the PostgreSQL server to remote connections.
The text was updated successfully, but these errors were encountered: