Versions Compared

Old Version 115

changes.mady.by.user Otis Gospodnetić

Saved on

compared with

New Version 116

changes.mady.by.user Otis Gospodnetić

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

How do I configure Collectd for SPM if I am already using it?

A: SPM requires the Collectd "csv" plugin to be enabled and configured like this:

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
languagebash
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: SPM depends on Collectd to display system metrics. If SPM was showing your system metrics in the past and has now stopped, first check if Collectd is still installed and running. Also check suggestions from "I rebooted my server and now I don't see any data in my graphs. What should I check?" If SPM never showed system metrics for your application, it may be that Collectd wasn't installed or running at the time when you installed SPM client. In that case, ensure Collectd is installed and running and after that re-run SPM client installer for your application.I am using SPM for Solr

I registered for SPM more than 5 minutes ago and I don't see

...

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?

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.

I am using SPM for Elasticsearch monitor and I don't see Index (and/or Refresh/Flush/Merge) stats, why is that?

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.

I registered for SPM more than 5 minutes ago and I don't see ANY of my data / I am getting errors when starting SPM Sender or Monitor, what should I check?

...

sudo /etc/init.d/spm-sender restart

and restart SPM Monitor by restarting your server which is being monitored (in case in-process/javaagent variant of SPM Monitor) or (in case of standalone SPM Monitor installation):

...

ANY of my data / I am getting errors when starting SPM Sender or Monitor, what should I check?

A: Here are a few things to check and do:
  1. Log into your monitored servers and make sure Collectd and SPM Sender are running.
  2. Check if system time is correct. If not, you should adjust the time, restart the SPM Sender with:
    sudo /etc/init.d/spm-sender restart

    and restart SPM Monitor by restarting your server which is being monitored (in case in-process/javaagent variant of SPM Monitor) or (in case of standalone SPM Monitor installation):

    sudo /etc/init.d/spm-monitor restart
  3. Make sure disks are not full.

  4. Make sure user spmsender can have more than 1024 files open:

    Code Block
    languagebash
    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.

  5. Check if hostname of your server is defined in /etc/hosts
  6. If you are starting your Jetty (or some other server) with command like "java ... -jar start.jar ..." and using inprocess (javaagent) version of monitor, make sure -D and -javaagent definitions occur before "-jar start.jar" part in your command
  7. If none of the suggestions helped, run sudo bash /opt/spm/bin/spm-client-diagnostics.sh to generate diagnostics package and send it to spm-support@sematext.com

...

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?

...

 

How come Disk Space Usage report shows more free disk space than df command?

A: SPM reports both free and reserved disk space as free, while df does not include reserved disk space by default.

 

I changed my server's hostname and now I don't see new data in my graphs. What should I do?

A: Simply restart SPM Sender:

 

Code Block
languagebash
sudo /etc/init.d/spm-sender restart

 

Can I specify which Java runtime the SPM client should use?

A: Yes, you can edit the /opt/spm/properties/java.properties file where you can specify the location of Java you want the SPM client (the SPM Sender, and SPM monitor if you are running the standalone version) to use.

Can SPM client use HTTP instead of HTTPS to send metrics from my servers?

A: Yes. Since version 1.22.0, SPM sender by default uses HTTPS to send metrics data to Sematext servers. If you prefer to use HTTP instead (for example, if you are running SPM on premises or if you don't need metric data to be encrypted when being sent to SPM over the Internet), you can adjust that in /opt/spm/properties/spm-sender.properties by changing protocol to http in property:

Code Block
spm_sender_receiver_url=https://spm-receiver.sematext.com/receiver/v1

 

...

How do I enable JMX in Solr?

A: Add or uncomment the <jmx/> directive in 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 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

 and restart Solr.  See http://wiki.apache.org/solr/SolrJmx for

more info

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?

A: SPM collects index stats from primary shards only.  To see the total number of documents in an index, select all shards in that index and choose "sum".  The list of shards and the "sum" function can be found in the "Shard filter" in the Index Stats report.

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. the "Shard filter" in the Index Stats report.

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. 

 

I am using SPM for Elasticsearch monitor and I don't see Index (and/or Refresh/Flush/Merge) stats, why is that?

 

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.

HBase Monitoring

How do I enable JMX in HBase?

...