Introduction

In this third example of combining different sets of statistical figures we are going to show you an interesting combination where you see the server latency information in combination with the DB access figures as well with the Total CPU utilization value which comes from the Platform statistics.

The time how long it takes to access a specific IBM Notes Database correlates with the server latency. So if the server latency is high (for whatever reasons) the results coming from the DB Access sensor will be high as well meaning that the DB has no issue rather that the connectivity towards the Domino Server is the bottleneck for a possible poor performance.

However if the server latency is fine, but the figures coming from the DB access sensor are still high then it would make sense that the bad performance correlates with the figures coming from the Total CPU utilization. This is just one idea out of dozens.

Example

Configuration

Create a Domino DB Access sensor

In this example we create again a simple Domino DB Access sensor definition where the sensor should open a random document within the People View of the names.nsf. 

 

Last but not least, specify all your servers which you want to monitor as well provide a certain schedule for the sensor.

 

Create a Domino Availability sensor

This is one of the simplest Sensor types because you need to specify at least the Targets you want to monitor and a schedule.

 

Create a Domino Statistic sensor

Specify the same Targets as well the same schedule like in the two previous Sensors.

 

So you should end up with three active sensors

 

Create a Line Chart

Now let’s create a line chart.

-Select a Line Series (Data Series Type) and choose the Domino Availability Sensor which you have created in the previous step.

-Select greenlight.availability.latency.total and click Next

-Disable Ascending Value Filter and click Finish

-
Drag & Drop again a Line Series (Data Series Types) and choose the Domino DB Access Sensor

-Select greenlight.dbaccess.database.document.time.to_document and click Next

-Disable also Ascending Value Filter and click Finish

-Drag & Drop again a Line Series (Data Series Types) and choose the Domino Statistics Sensor

-Select Platform.Process.ActiveDomino.TotalCpuUtil and click Next
(in case you don’t see any Platform statistics, make sure you have them enabled on your Domino Server)

-Disable also Ascending Value Filter and click Finish

 

You should have now the following picture (with different sensor names)

 

-Make sure to add the correct Target as well to specify a schedule and a name for this charting definition.

-Whenever you have done this, just click on generate the chart.

 

(In that chart example you can leave the Y-axes as they are)

Outcome:

 

Conclusion

This is just one chart example where we combined data from three different sensors into one graphical depiction.

In the above chart we see, that the latency is pretty fine with average of around 20ms. However the DB access sensor tells us that from time to time it takes ten times longer to access a document in the names.nsf. Interestingly this happens always whenever the CPU utilization increases a’ lot.

This does not tell you more, but it gives you an indication that a certain Domino Tasks grabs a’ lot of resources at this particular time. As an action you can create a second chart where you draw all CPU Utilization of all domino processes so that you see which of the domino processes takes most of the CPU resource.