Table of Contents |
---|
...
Code Block |
---|
<Plugin csv> DataDir /opt/spm/collectd/logs StoreRates true </Plugin> |
If you are already using Collectd and if the DataDir is already pointed to some other directory, simply symlink the /spm/collectd/logs directory to the directory specified in DataDir, like this:
Code Block | ||
---|---|---|
| ||
sudo mkdir -p /opt/spm/collectd # if needed sudo ln -s /some/existing/collectd/data/dir /spm/collectd/logs |
You will also have to merge the remaining part of the Collectd config required by SPM.
Is there a Chef Recipe for the SPM client
...
I rebooted my server and now I don't see any data in my graphs. What should I check
...
I am using SPM for Solr and I don't see any data on Solr and JVM reports, what is the problem
A: You should probably enable JMX in your Solr. Add or uncomment the <jmx /> directive in solrconfig.xml and restart Solr. See http://wiki.apache.org/solr/SolrJmx for more info.
I am using SPM for Solr and I don't see any data only in Solr Components or Errors reports, what should I do
A: Most likely you are using standalone variant of Solr monitor. In that case, SPM monitor can't collect metrics which are available only when running in-process. If so, switch to in-process (javaagent) version of SPM monitor.
Elasticsearch Monitoring
Why doesn't the number of documents I see in SPM match the number of documents in my Elasticsearch index
...
Can SPM collect metrics even when Elasticsearch HTTP API is disabled
Code Block |
---|
http.host: "127.0.0.1" |
Can I point SPM monitor to a non-localhost Elasticsearch node
My Elasticsearch is protected by basic HTTP authentication, can I use SPM
Code Block |
---|
SPM_MONITOR_ES_NODE_BASICAUTH_USERNAME=yourUsername SPM_MONITOR_ES_NODE_BASICAUTH_PASSWORD=yourPassword |
Restart your SPM monitor after this change (either with sudo /etc/init.d/spm-monitor restart in case of standalone monitor or by restarting Elasticsearch node if you are using in-process javaagent).
I am using SPM for Elasticsearch monitor and I don't see Index (and/or Refresh/Flush/Merge) stats, why is that
A: SPM for Elasticsearch monitor collects Index stats only from primary shards, so it is possible that you installed SPM monitor on some Elasticsearch node which hosts only replicas. The same is also true for Refresh/Flush and Merge stats. Also note that SPM Elasticsearch monitor should be installed on all your Elasticsearch nodes to get the complete picture of your cluster in SPM Reports UI....