Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SolarWinds SAM monitoring PostgreSQL

Hi all,

Does anyone successfully monitor the PostgreSQL server using SolarWinds SAM? Using Out Of the Box PostgreSQL template, I am running into an issue. I followed the following documentation, but it is not working. I opened up a support ticket and no luck yet. I double-checked all the configurations according to the documentation and spent a lot of hours, and still not able to monitor. To match the instruction in the documentation I even installed PostgreSQL 9 (No success), whereas I have to monitor PostgreSQL 11.

PostgreSQL
documentation.solarwinds.com/.../sam-postgresql-sw5792.htm

Configure Linux/Unix systems for monitoring by the SolarWinds Platform agent in SAM: PostgreSQL
documentation.solarwinds.com/.../sam-agent-linux-environment-configuration.htm

I get an error, "[IM002] [unixODBC][Driver Manager]Data source name not found, and no default driver specified" on all of the monitoring components. I can successfully manually test the connection from system DSN and User DSN, but when I use the same credential and configuration to monitor using SolarWinds SAM, It throws an error.

Any help is appreciated. TIA

Test manually - system DSN and user DSN (Using 32bit)

Find more posts tagged with

Accepted answers

All comments

PatrickRG

Did you have any luck getting this SAM template to work? I was asked to monitor a PostgreSQL 15 instance but it seems like no one has gotten this to work in awhile.

mandevil

Did you install the postgres-odbc driver also on the linux host? Think it was step 3 of the instructions (in addition to the unixODBC driver)... Not sure if you are leveraging DPA as a SWI solution, but if you are, it supports monitoring PostgreSQL and does ship with needed drivers (so shouldn't run into this type of issue). I know I've configured Oracle monitoring from SAM, but did it agentless by installing an Oracle client on my poller - didn't see that as an option in the instructions.

PatrickRG

I haven't tried yet. I was just researching the setup needed for the SAM template. Our PostgresSQL install is on a Windows box though.

chad.every

The less intuitive side is understanding how SolarWinds server to remote server connectivity works in SAM.

When you edit an Application Template, there is an 'Advanced' section that you can expand out that outlines the preferred polling method.

It defaults to 'agent' and automatically falls-back to 'agentless'.

That means the following

If Agent is installed on remote server --> ODBC drivers need to be installed on remote server. The Agent runs the DB connection from the remote server.
If Agent is not installed on remote server --> ODBC drivers need to be installed on the SolarWinds server. The SolarWinds servers runs the DB connection.

This means you can have a single application template and see different results based on what nodes it is assigned to. You can force the entire template to be 'agentless' and then ALL components in that template would be run from the SolarWinds server. Sometimes that is desirable, sometimes it in not. It all depends on what you're looking to solve.

PatrickRG

Thanks. That's great info!