So you have MSSQL databases and you’d like to keep an eye on the performance of your DB. Using NetEye this is quite easy. The tools you need are already available on your NetEye server: InfluxDB, the Telegraf agent, and Grafana for visualizing your Dashboards.
The SQL Server Input Plugin provides metrics for your SQL Server instance. It currently works with SQL Server versions 2008 and later. Recorded metrics are lightweight, and employ the dynamic management views supplied by SQL Server. What you need then is a login for your SQL Server created more or less with the following commands:
USE master;
GO
CREATE LOGIN [neteye] WITH PASSWORD = N'mystrongpassword';
GO
GRANT VIEW SERVER STATE TO [neteye];
GO
GRANT VIEW ANY DEFINITION TO [neteye];
GO
On your NetEye server, create a config file (/etc/telegraf/telegraf_mssql.conf) for Telegraf using this template:
Now start a Telegraf agent using that config file. Telegraf will immediately start sending data to InfluxDB. Then go to Grafana and import an “official” Dashboard using the number 4730. You will now have a very nice dashboard with all the performance data for your DB instance.
The dashboard provides KPI’s and graphs for metrics collected in real time by the Telegraf agent and stored in InfluxDB:
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix. Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Author
Juergen Vigna
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix. Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
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
Just like last year, we had the wonderful opportunity to attend FOSDEM, the most important open source conference in Europe. This year was no exception, and among the many exciting talks, one that particularly caught my attention was Alex Stefanini’s Read More
When designing an Elasticsearch architecture, choosing the right storage is crucial. While NFS might seem like a convenient and flexible option, it comes with several pitfalls when used for hosting live Elasticsearch data (hot, warm, cold, and frozen nodes). However, Read More