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.
Choosing the right backup solution is critical for system administrators and IT professionals. The upcoming NetEye 4.41 version will bring an update to MariaDB, moving from version 10.3 to 10.11. This makes it especially timely to explore the opportunities offered Read More
In NetEye environments we use Tornado to collect events, elaborate on them, and send notifications based on them from a lot of sources (syslog, email, SNMP traps and so on). In this article I'd like to suggest a different use Read More
As technology continually evolves, keeping our software stack up to date is essential for performance, security, and access to new functionalities. In this post, I want to share how we upgraded MariaDB from version 10.3 to 10.11 as part of Read More
In some test or development environments, you may need to simulate the presence of GSM modems without having an actual physical device. This can be useful for example when testing monitoring checks, SMS management systems, or creating new notification rules. Read More
Our older customers surely know that, in its earliest releases, NetEye 4 had no support for multitenancy. From a data perspective, there's just one big bin we throw everything into to be used later. Then, a debate about multitenancy began. Read More