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 IT Italy, 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 IT Italy, 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.
Running Ollama locally or on dedicated hardware is straightforward until you need to know whether a model is actually loaded in RAM, how fast it generates tokens under load, or when memory consumption reaches a threshold that affects other workloads. Read More
Hi everyone! Today I'd like to share with you an investigation we undertook related to ingesting Open Telemetry data in Elasticsearch, while maintaining tenant segregation from start to end. The Scenario Let's imagine we have multiple customers, where in this Read More
SNMP monitoring is the standard method for obtaining information and metrics from network devices. Typically, we focus on extracting data from a single interface to monitor its status, traffic, or errors. But in many cases, we’re only interested in getting Read More
In the ITOA module we fixed a bug that prevented the Performance Graphs to be shown in the Monitoring host and service page. List of updated packages grafana, grafana-autosetup, grafana-configurator and grafana-neteye-config to version 12.4.1_neteye3.29.2-1
Creating a GitHub organization is easy. Creating a public one that is actually well-structured, secure, and maintainable over time… not so much. At the beginning, it feels like a simple task: create the org, push some repositories, maybe define a Read More