Versions Compared

Old Version 194

changes.mady.by.user Otis Gospodnetić

Saved on

compared with

New Version 195

changes.mady.by.user Otis Gospodnetić

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

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

...

A: To see metrics for Kafka Producers, Brokers, and Consumers make sure to run SPM client on all of them.  Each of them has its own metrics.  Kafka Brokers do not expose Producers' or Consumers' metrics, so ensure you have SPM client on all three Kafka tiers.

Can I see metrics for non-Scala/JVM Kafka Producers and Consumers

A: No, because none of them seem to expose metrics the way Kafka's own Producer and Consumer implementations expose metrics.

AWS Monitoring

Which IAM permissions are needed to fetch Amazon EC2, EBS and ELB metrics

When you create an AWS app, you need to provide the access key and secret for a user that can fetch metrics for EC2, EBS and/or ELB, depending on which of those you select to be monitored. We recommend creating a separate IAM user for this, with the minimum permissions:


Code Block
languagetext
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeInstances",
                "ec2:DescribeAddresses",
                "ec2:DescribeVolumes",
                "elasticloadbalancing:DescribeLoadBalancers",
                "cloudwatch:GetMetricStatistics"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}


The Describe* permissions are needed to identify the resources which need to be monitored (Instances and Addresses for EC2, Volumes for EBS and LoadBalancers for ELB), while GetMetricStatistics will allow SPM to fetch the actual metrics from CloudWatch.

Alerts

Can I send alerts to HipChat, Slack, Nagios, or other WebHooks

A: SPM let's one configure arbitrary Webhooks to call with Alert event information when Alert events are triggered. The details for HipChat integration are described herehas integrations for Slack, HipChat, PagerDuty, VictorOps, OpsGenie, BigPanda, general WebHooks, email, and more.  See Integrations. 

What are Threshold-based Alerts

A: Threshold-based alerts are classic alerts where you choose a metric and a numeric value (a threshold) that, when reached or crossed, triggers an alert.

What is Anomaly Detection

A: Anomaly Detection uses a number of statistical algorithms to determine if a metric has become anomalous, meaning that its recent values have become significantly different from the "base" – the normal/typical values of that metric.  An example of an anomaly is a sudden spike or a sudden dip in a metric value.  SPM can trigger alerts when such anomalies are detected.

What are Heartbeat Alerts

A: Heartbeat Alerts are extremely useful for keeping an eye on your applications.  You create a single Heartbeat Alert for each SPM App.  From then on, SPM will watch all instances of your application that are a part of that SPM App. Should SPM not hear from any one of your application's instances for more than N minutes, it will alert you.  N can be as low as 2 minutes and you choose it yourself when you create a Heartbeat Alert.  


...