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

Unable to Monitor MySQL process

We have setup monitoring on mySQL instance -5.7.9 using the new template MySQL (5.7.9 or later) for Linux/Unix.

We are unable to monitor one of the components of this template that is MySQL process. We have multiple instances running on each MySQL node. Each instance has a unique port.

I have tried SNMPWalk but in vain. Is there a way to monitor this component for each instance. Screenshot is attached for reference. Edit Application MySQL Multiple DB s Slave MySQL.png

Find more posts tagged with

mysql-5.7.9

Accepted answers

All comments

aLTeReGo

Is the node managed via SNMP?

onsia

Yes, SNMP is being used.

aLTeReGo

Can you launch the Real-Time Process Explorer from the Node Details view of that MySQL server?

onsia

I was able to launch Real Time Process Explorer. But unfortunately it keeps looking for process and does not return any result.Is there anything that I have missed?

aLTeReGo

It sounds like there may be an issue with the SNMP Daemon or the view level permissions for the community string provided. What SNMP Daemon are you running on that Linux machine, and how is it configured?

onsia

Can you please provide more details

- Which SNMP Daemon should be used

- what permission levels are required.

- What configurations are recommended.

Thanks for the help.

aLTeReGo

- Which SNMP Daemon should be used

The latest version of NET-SNMP should be used

- what permission levels are required.

I would recommend a read-only view with access to the '.1" OID and all sub-branches.

- What configurations are recommended.

When troubleshooting simpler is always better. I would recommend trying a simple SNMPv2 read-only community string with no view restrictions first. Once that works you can increase the restrictions incrementally until you find the issue which is preventing you from access the hrSWRunTable OIDs.