Products :: SPM :: Troubleshooting
Sematext Scalable Performance Monitoring is brand new and we are
working on gathering troubleshooting items - let us know if you have
any questions!
Q: What should I do if I can't find the answer to my question here?
Q: I see only my systems metrics (e.g. CPU, Network, Disk...), but where is the rest of my data?
A: Make sure you have added the SPM agent to
your Java process command line and restarted the monitored
application. The information about how to add the SPM agent is
printed on the console during the installation and was also
captured in /tmp/spm-install.log .
Q: I registered for SPM more than 5 minutes ago and I don't see any of my data, what should I check?
A: Here are a few things to check and do:
- Log into your monitored servers and make sure Collectd and SPM Sender are running.
- Make sure disks are not full.
- Make sure user
spmsender can have more than 1024 files open:
sudo vim /etc/security/limits.conf
spmsender - nofile 32000
sudo vim /etc/pam.d/su
session required pam_limits.so
Restart SPM Sender after the above changes.
- Run bash /spm/bin/spm-client-diagnostics.sh script and send us the resulting ZIP file.
Q: I rebooted my server and now I don't see any data in my graphs. What should I check?
A: Here are a few things to check and do:
- Make sure Collectd is running: sudo service collectd restart. Make sure Collectd is set up to start at boot.
- Make sure SPM Sender is running: sudo /etc/init.d/spm-sender restart
- Make sure disk is not full: df -h
- Make sure maximal open files limit was not reached: see FAQ entry above
Q: How do I install Collectd?
Q: I see a server is using swap, but the swap I/O graph is empty - how can that be?
A:
You may be using an old version of Collectd. A bug with
incorrect swap I/O values was
fixed in
Collectd 4.10. Make sure you are using Collectd 4.10 or
newer. You can install/upgrade Collectd with yum, apt-get,
etc., or you can download a version from
http://collectd.org/download.shtml.