This extension can be used to query an ANSI SQL compliant database and the resulting values can be used as metrics on AppDynamics. The connection to the database is established through a JDBC connect and you will have to use a "connector" JDBC driver jar file in order to have the extension connect and query the database.
The metrics reported by the extension can be modified as per the user's requirements. This extension can be used to query and pull metrics from any SQL based database.
<MachineAgent_Dir>/monitors/The metricPrefix of the extension has to be configured as specified here. Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller.
Note: You will need to provide your own JDBC driver for the database you want to connect to. Put the driver JAR file in the same directory and add it to the classpath element in the monitor.xml file!
<java-task> <!-- Use regular classpath foo.jar;bar.jar --> <!-- append JDBC driver jar --> <classpath>sql-monitoring-extension.jar;Jar-File-For_Your-DB.jar.jar</classpath> <impl-class>com.appdynamics.extensions.sql.SQLMonitor</impl-class> </java-task>
<task-arguments> <!-- config file--> <argument name="config-file" is-required="true" default-value="monitors/SQLMonitor/config.yml" /> .... </task-arguments>
Note:Please make sure to not use tab (\t) while editing yaml files. You may want to validate the yaml file using a yaml validator http://yamllint.com/
You will have to Configure the SQL server instances by editing the config.yaml file in
<MACHINE_AGENT_HOME>/monitors/SQLMonitor/. The information provided in this file will be used to connect and query the database. You can find a sample config.yaml file below.
# Make sure the metric prefix ends with a | #This will create this metric in all the tiers, under this path. #metricPrefix: "Custom Metrics|SQL|" #This will create it in specific Tier. Replace <ComponentID> with TierID metricPrefix: "Server|Component:<ComponentID>|Custom Metrics|SQL|" dbServers: - displayName: "Instance1" connectionUrl: "" driver: "" connectionProperties: - user: "" - password: "" #Needs to be used in conjunction with `encryptionKey`. Please read the extension documentation to generate encrypted password #encryptedPassword: "" #Needs to be used in conjunction with `encryptedPassword`. Please read the extension documentation to generate encrypted password #encryptionKey: "welcome" # Replaces characters in metric name with the specified characters. # "replace" takes any regular expression # "replaceWith" takes the string to replace the matched characters metricCharacterReplacer: - replace: "%" replaceWith: "" - replace: "," replaceWith: "-" queries: - displayName: "Active Events" queryStmt: "Select NODE_NAME, EVENT_CODE, EVENT_ID, EVENT_POSTED_COUNT from Active_events" columns: - name: "NODE_NAME" type: "metricPathName" - name: "EVENT_ID" type: "metricPathName" - name: "EVENT_CODE" type: "metricValue" - name: "EVENT_POSTED_COUNT" type: "metricValue" - displayName: "TRANSACTION DATABASE" queryStmt: "SELECT TARGET_BOX, REACH_DURATION, ROUTER_DURATION FROM ASG_TRANSACTIONS WHERE TARGET_BOX IN ('target1','target2','target3','target4','target5')" columns: - name: "TARGET_BOX" type: "metricPathName" - name: "REACH_DURATION" type: "metricValue" - name: "ROUTER_DURATION" type: "metricValue" - displayName: "Node Status" queryStmt: "Select NODE_NAME, NODE_STATE from NODE_STATES" columns: - name: "NODE_NAME" type: "metricPathName" - name: "NODE_STATE" type: "metricValue" properties: convert: "INITIALIZING" : 0 "UP" : 1 "DOWN" : 2 "READY" : 3 "UNSAFE" : 4 "SHUTDOWN" : 5 "RECOVERING" : 6 numberOfThreads: 5 #Run it as a scheduled task instead of running every minute. #If you want to run this every minute, comment this out #taskSchedule: #numberOfThreads: 1 #taskDelaySeconds: 120
Lets take a look at some sample connection information:
dbServers: - displayName: "Instance1" connectionUrl: "jdbc:sqlserver://192.168.57.101:1433;user=bhuv;password=12345;databaseName=frb-test;" driver: "com.microsoft.sqlserver.jdbc.SQLServerDriver" # connectionProperties: # - user: "" # - password: ""
In order to connect to any database, you will have to provide a connectionUrl. In the example above we see that the extension is connected to the "sqlserver"(listed in the config) using the connectionUrl. In this case we are also providing the username, password and the databaseName in the same connectionUrl and therefore the "connectionProperties" and the fields under it, "user" and "password", are commented out. You have to make sure that if you are not sending any connectionProperties to create a connection, then you should comment the whole thing out just like in the example.
As this may not be the same for other types of SQL based systems, lets take a look at another way you can connect to the database. In this case we do need to provide properties such as a username and a password and therefore we uncomment those lines and update them with valid information.
dbServers: - displayName: "Instance2" connectionUrl: "jdbc:vertica://192.168.57.102:5433/VMart" driver: "com.vertica.jdbc.Driver" connectionProperties: - user: "dbadmin" - password: "password"
In this case we do add the Database Name as the last part of the connectionUrl (VMart) but all other properties like the username and password are provided as connectionProperties. You will have to confirm how your database takes in the login information and based on that provide the information in your config.yaml in order to successfully establish a connection.
Only queries that start with SELECT are allowed! Your query should only return one row at a time.
It is suggested that you only return one row at a time because if it returns a full table with enormous amount of data, it may overwhelm the system and it may take a very long time to fetch that data.
The extension does support getting values from multiple columns at once but it can only pull the metrics from the latest value from the row returned.
The name of the metric displayed on the Metric Browser will be the "name" value that you specify in the config.yml for that metric. Looking at the following sample query :
queries: - displayName: "Active Events" queryStmt: "Select NODE_NAME, EVENT_CODE, EVENT_ID, EVENT_POSTED_COUNT from Active_events" columns: - name: "NODE_NAME" type: "metricPathName" - name: "EVENT_ID" type: "metricPathName" - name: "EVENT_CODE" type: "metricValue" - name: "EVENT_POSTED_COUNT" type: "metricValue"
For the query listed above, there will be two metrics returned as we have two columns of type "metricValue". The metric path for them will be :
Lets look at another query.
- displayName: "Node Status" queryStmt: "Select NODE_NAME, NODE_STATE from NODE_STATES" columns: - name: "NODE_NAME" type: "metricPathName" - name: "NODE_STATE" type: "metricValue" properties: convert: "INITIALIZING" : 0 "UP" : 1 "DOWN" : 2 "READY" : 3 "UNSAFE" : 4 "SHUTDOWN" : 5 "RECOVERING" : 6
Lets say if your query returns a text value, but you would still like to see it in the metric browser. In order to make that happen, you could use the "convert" property and assign each value a number. The extension will automatically convert the text value to the corresponding number.
NOTE: In order to use this feature, please make sure that the value that is being returned is EXACTLY the same as you have listed in the config.yaml, otherwise the extension will throw an error.
Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.
If you want to use password encryption, please send arguments as "connectionProperties". You will have to fill in the encryptedPassword and encryptionKey fields in the config.yml file but you will also have to give an empty string value i.e. "" in the password field and the encrypted password will be automatically picked by the extension.
Workbench is an inbuilt feature provided with each extension in order to assist you to fine tune the extension setup before you actually deploy it on the controller. Please review the following document on How to use the Extensions WorkBench
If after going through the Troubleshooting Document you have not been able to get your extension working, please file a ticket and add the following information in order so that we can assist you better and faster.
Please provide the following in order for us to assist you better.
<MachineAgent>/conf/logging/log4j.xml. Change the level value of the following
<logger>elements to debug.
For any support related questions, you can also contact firstname.lastname@example.org.
Always feel free to fork and contribute any changes directly via GitHub.
3.7 or Later
SQL Version Tested On:
SQLServer 4.1,4.2, Vertica
Last updated On: