| 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
...
A: Filters have 1 day granularity, which means that a server will be listed under Hosts filter until 24 hours since it last sent data have passed. For example, if a server stopped sending data at 1 PM and if at 8 PM you are looking at the last 6 hours of data (for a period from 2 PM until 8 PM) you will not see data from this server on the graph, but you will still see this server listed under the Hosts filter until 1 PM on the following day. After 1 PM on the following day this server should disappear from the Hosts filter.
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
A: Each SPM agent collects Elasticsearch metrics only from the local node by accessing the Stats API via HTTP. To allow only local access add the following to elasticsearch.yml. Don't forget to restart each ES node to whose elasticsearch.yml you add this.
| Code Block |
|---|
http.host: "127.0.0.1" |
Can I point SPM monitor to a non-localhost Elasticsearch node
A: Yes. Adjust /opt/spm/spm-monitor/conf/spm-monitor-config-TOKEN-_HERE-default.properties and change the SPM_MONITOR_ES_NODE_HOSTPORT property from the default localhost:9200 value to use an alternative hostname:port. After that restart SPM monitor (if you are running a standalone version) or Elasticsearch process(es) with embedded SPM monitor.
My Elasticsearch is protected by basic HTTP authentication, can I use SPM
A: Yes. You just need to adjust /opt/spm/spm-monitor/conf/spm-monitor-config-TOKEN_HERE-default.properties file by adding the following two properties (replace values with your real username and password):
| Code Block |
|---|
SPM_MONITOR_ES_NODE_BASICAUTH_USERNAME=yourUsername
SPM_MONITOR_ES_NODE_BASICAUTH_PASSWORD=yourPassword |
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....