Ensure you have INstalled the Infrastructure Agent, see this guide for more information.
- Ensure that you have a Microsoft SQL Server user with user privileges for both CONNECT and VIEW SERVER STATE, and READ access permissions.
- Ensure that you have installed and ACTIVATED the integration by following these 5 steps that are outlined here.
- Make sure that each monitored server has a unique hostname to avoid inaccurate metrics from combining multiple servers under a single hostname. You can use the optional display_name setting to override the default hostname.
- In the mssql-config.yml ensure that you are abiding by the correct YAML format and syntax. YAML is very sensitive to syntax errors and spaces. Look here for an example configuration to follow. Parsing the logs for any
error="yamlentries will be a good check to run to ensure your YAML is correctly formatted.
- In the mssql-config.yml configuration file double check that the username and passwords are correct.
- Check if the port in which the MSSQL server is listening is correct.
- If SSL is used to successfully connect to your MSSQL Server then make sure that the enable_ssl flag is set to TRUE in your mssql-config.yml configuration file.
- Remove any default sample values from the mssql-config.yml configuration file that you are not using
- If you are noticing issues with not being able to pull the data for the custom query you have written within the mssql-config.yml configuration file ensure that the format is correct. There are great examples of how to format your query here. Also ensure that the user created in step 7 above has access to the table you are trying to query.
- If using a separate
mssql-custom-query.ymlfile to house numerous SQL queries then ensure the formatting is correct for this file. An example of how this mssql-custom-query.yml should look can be found here. If using the
mssql-custom-query.ymlfile option then also make sure the
custom_metrics_query:option in the mssql-config.yaml file is replaced with
- Check if your MSSQL data is reporting by checking INFRASTRUCTURE -> THIRD-PARTY SERVICES -> MSSQL or running NRQL queries against the following 3 event types: MssqlDatabaseSample, MssqlInstanceSample, MssqlWaitSample