The New Relic integration for MS SQL Server captures critical performance metrics and inventory reported by a SQL Server Instance. Data on the SQL Server Instance and Databases is collected.
Inventory and metric data is collected via SQL queries to the Instance.
A user with the necessary permissions to collect all the metrics and inventory can be configured as follows
USE master;
CREATE LOGIN newrelic WITH PASSWORD = 'tmppassword';
CREATE USER newrelic FOR LOGIN newrelic;
GRANT CONNECT SQL TO newrelic;
GRANT VIEW SERVER STATE TO newrelic;
-- Goes through each user database and adds public permissions
DECLARE @name NVARCHAR(max)
DECLARE db_cursor CURSOR FOR
SELECT NAME
FROM master.dbo.sysdatabases
WHERE NAME NOT IN ('master','msdb','tempdb','model')
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name WHILE @@FETCH_STATUS = 0
BEGIN
EXECUTE('USE "' + @name + '"; CREATE USER newrelic FOR LOGIN newrelic;' );
FETCH next FROM db_cursor INTO @name
END
CLOSE db_cursor
DEALLOCATE db_cursorFor installation and usage instructions, see our documentation web site.
To add custom queries, use the -custom_metrics_query option to provide a single query, or the -custom_metrics_config option to specify a YAML file with one or more queries, such as the sample mssql-custom-query.yml.sample
Each query that returns a table of values will be parsed row by row, adding the MssqlCustomQuerySample event as follows:
- The column name is the attribute name
- Each row value in that column is the attribute value
- The metric type is auto-detected whether it is a number (type GAUGE), or a string (type ATTRIBUTE)
One customizable attribute in each row can be configured by database values using the following names:
- The column
metric_namespecifies its attribute name - The column
metric_valuespecifies its attribute value - The column
metric_typespecifies its metric type, i.e.gaugeorattribute
For example, the following query makes attributes named category_0, category_1, category_2 and so on.
SELECT CONCAT('category_', category_id) AS metric_name, name AS metric_value, category_type FROM syscategoriesWhen using a YAML file containing queries, you can specify the following parameters for each query:
query(required) contains the SQL querydatabase(optional) PrependsUSE <database name>;to the SQL, and adds the database name as an attributeprefix(optional) prefix to prepend to the attribute namemetric_name(optional) specify the name for the customizable attributemetric_type(optional) specify the metric type for the customizable attribute
Check the official documentation website for compatibility and requirements.
Golang is required to build the integration. We recommend Golang 1.11 or higher.
After cloning this repository, go to the directory of the MSSQL integration and build it:
$ makeThe command above executes the tests for the MSSQL integration and builds an executable file called nri-mssql under the bin directory.
To start the integration, run nri-mssql:
$ ./bin/nri-mssqlIf you want to know more about usage of ./bin/nri-mssql, pass the -help parameter:
$ ./bin/nri-mssql -helpTo run the tests execute:
$ make testTo develop locally on M1 we need to leverage a different image, having few limitations and forward the port:
version: '3.1'
services:
mssql:
image: mcr.microsoft.com/azure-sql-edge
ports:
- "1433:1433"
container_name: mssql
environment:
ACCEPT_EULA: Y
SA_PASSWORD: secret123!
MSSQL_PID: Developer
restart: alwaysTo connect with a msclient simply start the service:
$ docker-compose up
$ sqlcmd -S127.0.0.1 -USA -Psecret123! -q "SELECT * FROM sys.dm_os_performance_counters WHERE counter_name = 'Buffer cache hit ratio' or counter_name = 'Buffer cache hit ratio base'"To install sqlcmd you could run:
$ brew tap microsoft/mssql-release https://github.com/Microsoft/homebrew-mssql-release
$ brew update
$ brew install mssql-toolsObviously, you could also run the integration and leverage the debugger.
Should you need assistance with New Relic products, you are in good hands with several support diagnostic tools and support channels.
New Relic offers NRDiag, a client-side diagnostic utility that automatically detects common problems with New Relic agents. If NRDiag detects a problem, it suggests troubleshooting steps. NRDiag can also automatically attach troubleshooting data to a New Relic Support ticket.
If the issue has been confirmed as a bug or is a Feature request, please file a Github issue.
Support Channels
- New Relic Documentation: Comprehensive guidance for using our platform
- New Relic Community: The best place to engage in troubleshooting questions
- New Relic Developer: Resources for building a custom observability applications
- New Relic University: A range of online training for New Relic users of every level
At New Relic we take your privacy and the security of your information seriously, and are committed to protecting your information. We must emphasize the importance of not sharing personal data in public forums, and ask all users to scrub logs and diagnostic information for sensitive information, whether personal, proprietary, or otherwise.
We define “Personal Data” as any information relating to an identified or identifiable individual, including, for example, your name, phone number, post code or zip code, Device ID, IP address, and email address.
For more information, review New Relic’s General Data Privacy Notice.
We encourage your contributions to improve this project! Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.
If you have any questions, or to execute our corporate CLA (which is required if your contribution is on behalf of a company), drop us an email at [email protected].
A note about vulnerabilities
As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.
If you would like to contribute to this project, review these guidelines.
To all contributors, we thank you! Without your contribution, this project would not be what it is today.
nri-mssql is licensed under the MIT License.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent