Versions Compared

Old Version 126

changes.mady.by.user Otis Gospodnetić

Saved on

compared with

New Version 127

changes.mady.by.user Bojan Šmid

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?

...

 

Code Block
spm_sender_proxy_host=
spm_sender_proxy_port=
spm_sender_proxy_user_name=
spm_sender_proxy_password=

 

When installing SPM client, I see "The certificate of `pub-repo.sematext.com' is not trusted" or similar error.  How can I avoid it?

A: There can be multiple reasons for this, most likely:

  • system time on your machine is not correct and adjusting it should fix the problem
  • you are installing SPM client as root user - in some cases that can cause this error and installing SPM client as a different user may help

If none of the above eliminates the problem for you try adding a flag to avoid certificate checking. In case the command with wget is failing in your case, add "--no-check-certificate" as wget argument. If command with curl is failing, add "-k" flag.

How do I create the diagnostics package?

A: In case you are having issues with SPM, you can create diagnostics package on affected machines where SPM client was installed by running:

Code Block
sudo bash /opt/spm/bin/spm-client-diagnostics.sh

The resulting package will contain all relevant info need for our investigation. You can send it, along with short description of your problem, to spm-support@sematext.com or contact us in chat.

I see only my system metrics (e.g. CPU, Memory, Network, Disk...), but where is the rest of my data?

...

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?

...