You can use open source monitoring solutions like Telegraf, InfluxDB, and Grafana to monitor your applications and databases running on-premises or on Amazon Elastic Compute Cloud (Amazon EC2). In this post, we explain how you can leverage these tools on Amazon Relational Database Service (Amazon RDS) Custom for SQL Server.
Use of open source software in application monitoring gives you the flexibility to further customize these tools for your specific monitoring needs. By utilizing an extensive range of supported Grafana data sources and Telegraf plugins, your monitoring solution can integrate metrics from various application components, such as CDNs, APIs, databases, networks, and firewalls, along with business key performance indicators (KPIs) into a single dashboard.
When moving from a self-managed SQL Server environment to a managed database solution like Amazon Relational Database Service (Amazon RDS) for SQL Server, you can monitor your database using integrated solutions like Amazon CloudWatch and Amazon RDS Performance Insights. These services provide many advantages over self-managed solutions. However, if you’re heavily invested in an agent-based monitoring solution, you may feel restricted because you can’t extend the same solution to Amazon RDS for SQL Server due to the lack of access to the underlying operating system.
Amazon RDS Custom is a managed database service for applications that require customization of the underlying operating system and database environment. You can now monitor Amazon RDS custom metrics in your existing monitoring solution. Because RDS Custom provides complete access to the underlying OS, you can install a variety of monitoring agents, such as Telegraf. This also enables you to have granular control over various metrics and customize your monitoring solution even further.
In this post, we explain how to implement this solution and improve observability for Amazon RDS Custom for SQL Server. Remember, to persist the changes made on your RDS Custom instance, you should create your own Custom Engine Version (CEV). The CEV feature allows you to use your own AMI as a basis for RDS Custom for SQL Server, and ensures your OS changes will persist in certain situations, such as a disk corruption.
Monitoring tools used in this post
To build a monitoring solution, Amazon RDS Custom allows you the flexibility to use a variety of open source or proprietary software’s which requires access to the underling operating system. We use the following open source software’s in this post:
InfluxDB – InfluxDB is an open source timeseries database. We use InfluxDB for storing metrics.
Telegraf – Telegraf is a server-based agent for collecting and sending metrics and events from databases, systems, and IoT sensors.
Amazon Managed Grafana – Amazon Managed Grafana is a fully-managed service for Grafana, a popular open-source analytics service. We are using Amazon Managed Grafana for the purpose of visualizing SQL Server metrics.
To monitor our RDS Custom for SQL Server instance, we install a Telegraf agent to collect and push SQL Server metrics into a time series database. For this post, we use Amazon EC2 and create an Ubuntu instance to run open-source InfluxDB as our time series database to store the metrics. To make monitoring and visualization simpler, we use Amazon Managed Grafana.
With this solution, you can achieve the following:
Gain access to the OS of your RDS Custom instance and deploy a monitoring agent (for this post, we demonstrate with Telegraf)
Configure the Telegraf agent and enable the SQL Server input plugin to collect database performance metrics from your RDS Custom instance and ingest the data into an InfluxDB database
Create a monitoring dashboard for SQL Server metrics in Amazon Managed Grafana.
The following diagram illustrates our solution architecture.
Deploy the required resources using AWS CloudFormation.
The template creates an IAM instance profile, AWS Key Management Service (AWS KMS) encryption key, and more resources. For more information, refer to Configure networking, instance profile, and encryption.
You can verify the resources on the Outputs tab on the AWS CloudFormation console, as shown in the following screenshot. Note the values for the KMS key, security group, and VPC, to use in later steps.
Create an RDS Custom instance
To create your RDS Custom instance, complete the following steps:
On the Amazon RDS console, choose Create database.
Select Standard create.
Select Microsoft SQL Server as the engine type.
For Database management type, select Amazon RDS Custom.
Select any SQL Server Edition
Under Settings¸ enter a name for the database and a primary user name and password.
For Instance configuration and storage, keep the default parameters.
Under Connectivity, choose the VPC and subnet you created with the CloudFormation template.
For VPC security group, select Choose existing and choose the security group created as part of the CloudFormation template.
Under RDS Custom security, choose the instance profile and the AWS KMS key created through the CloudFormation template.
Choose Create database and wait for Amazon RDS to provision the RDS Custom instance.
Deploy InfluxDB on an Ubuntu instance
Since InfluxDB is supported on multiple operating systems, we are using Ubuntu for this post. To deploy InfluxDB on an Ubuntu instance, complete the following steps:
Launch an EC2 instance with Ubuntu version 22 in the same VPC as the RDS Custom instance.
Log in to the EC2 instance and run the following commands to download and install InfluxDB 1.8.0:
update wget https://dl.influxdata.com/influxdb/releases/influxdb_1.8.10_amd64.deb
sudo dpkg -i influxdb_1.8.10_amd64.deb
systemctl start influxdb
systemctl enable influxdb
Optionally, you can run the following command to make sure that InfluxDB is running:
systemctl status influxdb
Because the InfluxDB instance is configured on port 8086, create an inbound rule in the security group of the InfluxDB EC2 instance to allow the RDS Custom instance on port 8086.
Create a database in InfluxDB
To create your database in InfluxDB, complete the following steps:
Connect to the terminal on Amazon EC2 and open the InfluxDB CLI with the following command:
This command brings up the InfluxDB CLI, as shown in the following screenshot.
Run the following command to create a database called sqlmonitoring:
create database sqlmonitoring
Optionally, you can verify that the database is created successfully by running the following command:
Create login credentials for InfluxDB and the Telegraf agent
By default, InfluxDB 1.8 has no authentication enabled. We enable authentication by creating an admin user. We also create another user named ‘telegraf‘. The telegraf agent running on RDS Custom server will use the ‘telegraf’ user account to send metrics data to the InfluxDB database. To create your users, complete the following steps:
Run the following command in the InfluxDB CLI to provision the users admin and telegraf:
CREATE USER admin WITH PASSWORD ‘password’ WITH ALL PRIVILEGES
CREATE USER “telegraf” WITH PASSWORD ‘[email protected]’
GRANT READ,WRITE ON sqlmonitoring TO telegraf
Verify if users are created successfully:
Set up your RDS Custom instance to enable RDP access
To allow remote desktop (RDP) access on your RDS Custom instance, complete the following steps:
Create an inbound rule in the security group of the RDS Custom instance to allow connections on the RDP port.
Connect to the RDS instance using Session Manager and run the following command to create a firewall rule to allow RDP traffic to the instance:
Set-NetFirewallRule -DisplayName “Remote Desktop – User Mode (TCP-In)” -Direction Inbound -LocalAddress Any -Profile Any
We use AWS Secrets Manager to store our credentials.
On the Secrets Manager console, locate the secret rds-custom.
Choose Retrieve secret value
Save the secret value as a .pem file.
Use this .pem file to get the password of the RDS custom instance.
Create a SQL server login for Telegraf
Next, we need to provision a login account in the SQL Server instance and provide sufficient privileges to access various system catalogs and dynamic management views (DMVs) to collect various SQL metrics.
RDP to the RDS Custom instance and open SQL Server Management Studio (SSMS).
Connect using the credentials provided during the RDS Custom instance creation.
Open a new query window and run the following query to create a SQL login with the necessary privileges to collect metrics:
CREATE LOGIN telegraf WITH PASSWORD = N’[email protected]′;
GRANT VIEW SERVER STATE TO telegraf;
GRANT VIEW ANY DEFINITION to telegraf;
Set up a Telegraf 1.23.2 agent on the RDS Custom instance
For the purpose of this post, we are using Telegraf version 1.23.2, but you should use the latest available version.
To set up Telegraf, complete the following steps:
RDP to the RDS instance and run the following script in Windows PowerShell:
## Download telegraf
Invoke-WebRequest https://dl.influxdata.com/telegraf/releases/telegraf-1.23.2_windows_amd64.zip -UseBasicParsing -OutFile telegraf.zip
## Expand the archive
## Create Directory structure for telegraf agent installation
mkdir ‘C:Program FilesInfluxDatatelegraf’
## Copy telegraf exe to ‘C:Program FilesInfluxDatatelegraf’
copy .telegraftelegraf-1.23.2telegraf.exe ‘C:Program FilesInfluxDatatelegraf’
Create a file called telegraf.conf in C:Program FilesInfluxDatatelegraf with the following configuration (provide the IP address of the InfluxDB EC2 instance):
Run the following command to install Telegraf as a Windows service:
“C:Program FilesInfluxDatatelegraftelegraf.exe” –service install –config “C:Program FilesInfluxDatatelegraftelegraf.conf”
On the Start menu, choose Run and enter services.msc.
Start the Telegraf Data Collector Service.
Verify data ingestion in InfluxDB
Access the Influx CLI and run the following commands to verify that the data pushed by the Telegraf agent is visible in the sqlmonitoring database:
You should see the following output when the Telegraf agent starts to ingest metrics into InfluxDB.
Set up a Grafana workspace
On the Amazon Managed Grafana console, make sure you’re in the same Region as the InfluxDB EC2 machine. You can follow the steps below to setup an Amazon Managed Grafana workspace.
Create a workspace
Setup VPC connectivity to allow connectivity with InfluxDB on EC2
Configure the workspace
Set up an InfluxDB data source in Grafana
To set up your data source in Grafana, complete the following steps:
Log in to your Grafana workspace.
Under Configuration in the navigation pane, choose Data sources.
Choose Add data source.
For Name, enter a name for your data source.
For Query Language, choose InfluxQL.
For URL, enter your InfluxDB instance URL.
In the InfluxDB Details section, enter the database name sqlmonitoring and enter the credentials of the telegraf user.
Choose Save & test.
Create a dashboard in Grafana
We now import the JSON to create a dashboard in Grafana for monitoring SQL Server metrics. You can further customize the dashboard panels and queries for your specific monitoring requirements.
Log in to your Grafana workspace.
In the left pane, hover the mouse on the + sign and choose Import.
There are multiple open source dashboards available on the Grafana Dashboard site. We recommend Dashboard ID: 9386
Enter dashboard ID 9386 into the ‘Import from Grafana.com’ text box
Choose the InfluxDB data source in the next window and choose ‘Import’
Once you finish importing the dashboard you will start seeing the SQL server metrics like the following screenshots.
To avoid incurring unwanted charges, delete the resources you created as part of this post. Refer to the following instructions:
RDS database – Deleting a DB instance
EC2 instance – Terminate your instance
Grafana workspace – Deleting a workspace
CloudFormation stack – Deleting a stack on the AWS CloudFormation console
In this post, we demonstrated a solution to set up SQL Server monitoring on an RDS Custom instance using Telegraf’s input plugin for SQL Server. We also demonstrated how you can configure InfluxDB and Amazon Managed Grafana for storing and visualizing metrics. Remember, in order to persist your changes on RDS Custom for SQL Server, you need to create a Custom Engine Version which allows you to use your own AMI as a basis for RDS Custom.
Try out the solution and if you have any comments or questions, leave them in the comments section.
About the Authors
Arun Pandey is a Senior Database Specialist Solutions Architect at AWS. With over 17 years of experience in application engineering and infra-architecture, Arun helps digitally-native companies in India build resilient and scalable database platforms, which aids in solving complex business problems and innovating faster on AWS.
Siddharth Joshi is a Technical Account Manager at AWS with 15 years of experience. At AWS, he works with ISV customers to help them achieve operational excellence, among other technical guidance. He is passionate about observability and automation.
Read MoreAWS Database Blog