You can also use Sumo to collect custom business and operational data that is coded into your organization’s applications.
In this lab, we will look at metrics from our TravelLogic Demo.
Let's begin by testing the Graphite Metrics Rule we just reviewed during Training.
First, let's query a metric using its raw Graphite name. In a metrics query, enter the following:
On a second query, run the following to query the exact same metric. However, this time, we are taking advantage of the key-value tags created by the Metrics Rule
You will notice you are graphing the exact same metric twice. You can check this by clicking on the Legend tab and verifying the metric's raw name, plus all other metadata fields.
Now let's learn how to use some additional operators. In the next steps we'll plot data from an online travel website to determine successful versus unsuccessful bookings.
In a new Metrics tab, add a query to search for all your successful bookings for the last 60 minutes:
In a second query underneath the first one, search for all failed bookings:
Click on the Settings tab to see what options are available to you. For example, you can change the chart type (line or area), the color palette used, the line width and the axes labels and scales.
Explore the Legend tab, which allows you to view all-time series detail for each metric charted.
Back in the query tab, toggle off the success.count by clicking on the orange icon (). This will now only chart the fail.count metric.
Any pink dots in your chart are identifying outliers in your data. You can edit the settings for your outliers by clicking the pink dot on the top right and editing the Outliers settings: how many outliers to show (Top) and how many standard deviations to use when considering outliers (Threshold).
Lastly, click on the 3 grey dots in the top right corner to view the query info, refresh the query, or add this chart to a Dashboard.
Let's now compare KPIs at different time periods using the timeshift operator. The timeshift operator shifts the time series of your query. It's very useful to compare across multiple time periods.
In a new Metrics tab, add a query to search for all your mean latency for the last 60 minutes.
Compare that with your latency from 1 day ago.
metric=latency.mean | timeshift 1d
Similar to logs, metrics have the usual operators (min, max, sum, count, avg). However, oftentimes, what you want to measure is change.
In this next exercise, we will identify rate of change to get early warning on impending issues.
In a new Metrics tab, add a query to search for a count of packets received in the last 60 minutes.
To find the difference between one data point and the next, edit your query to show the delta.
type=packets_received metric=count | delta
However, to find the rate of change, in this case, packets received per second, edit your query to:
type=packets_received metric=count | rate
With this last query, you're able to determine if the rate at which packets are being received is increasing gradually or spiking quickly. Identifying an outlier on a rate of change is a better indicator of an impending problem.
Lastly, let's learn how to correlate metrics to relevant logs to identify the root cause.
Metrics allow you to identify symptoms in your environment (WHAT is going on?). Relevant logs help you identify the cause (WHY is this happening?). Let's again look for successful and failed bookings, but this time, let's take a look at the relevant logs to identify why we have failed bookings.
Identify counts of successful booking and failed bookings for your travel website.
To overlay your metrics with the relevant logs, enter this log query as depicted below:
Notice the orange bars at the top. The darker the bar, the larger the number of logs containing the word ERROR. Click the bar to view the relevant logs in this same screen. Shift+click to view logs in a Log Search screen.