Due to the very positive customer feedback on our extended MSSQL performance
monitoring article, I would like to briefly highlight this functionality.
We have been implementing systems for MSSQL performance monitoring for a long
time, offered either as a managed IT service, or on-premise depending on the
requirements.
Previously, we recorded and evaluated counters such as CPU, memory KPI’s, I/O KPIs, performance counters, wait statistics, memory breakdowns, transaction log activity, etc. We would then frame them as a historical comparison for each counter individually.
Here’s a dashboard that illustrates what I mean:
Now let’s go one step further.
It’s clear that as soon as performance problems occur on a MSSQL database, these metrics are no longer sufficient for accurate error analysis. That’s why we’ve extended MSSQL performance monitoring to analyze long transactions, head blockers and deadlocks.
This means that we not only measure the number or duration, e.g. of long
transactions, but also the user, host name, etc. from which each
transaction was generated. This is an essential part of an effective
performance analysis by a DBA.
Here’s a screenshot showing an example Long Transactions analysis:
To implement this functionality, we again use InfluxDB with Grafana dashboarding. We fill the Influx database via the Telegraf agent, which runs on the MSSQL server and reads the necessary information from the MSSQL instance via the scripts we have created.
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Tobias Goller
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
This is that Time of the Year when you begin preparing all your SLA Reports to help you understand how your important services behaved during the year itself. It's like the end of a horse race, when the bets are Read More
When using Kibana in environments that require a proxy to reach external services, you might encounter issues with unrecognized SSL certificates. Specifically, if the proxy is exposed with its own certificate and acts as an SSL terminator, requests made by Read More
In a previous post we went through the configuration of Elastic Universal Profiling in NetEye, seeing how we can profile applications written in programming languages that do not compile to native code (for example Python, PHP, Perl, etc.) But what Read More
Elastic 8.16, which comes with NetEye 4.39, made Elastic Universal Profiling generally available for self-hosted installations. This means that NetEye SIEM installations will now be able to take advantage of the continuous profiling solution by Elastic. In this blog post Read More
In the first part of this series, we explored how Jira Service Management (JSM) helps streamline Incident Management, aligning with ITIL v4 best practices. Incident Management aims to restore normal service operation as quickly as possible after a disruption, ensuring Read More