Deployable on premise or in the cloud, SAP HANA is an in-memory data platform that lets you accelerate business processes, deliver more business intelligence, and simplify your IT environment. By providing the foundation for all your data needs, SAP HANA removes the burden of maintaining separate legacy systems and siloed data, so you can run live and make better business decisions in the new digital economy. HanaDB Monitoring Extension gathers metrics and sends them to the AppDynamics Metric Browser.
Either Download the Extension from the AppDynamics Marketplace or Download the Extension from the Github releases or Build from Source.
HanaDBMonitor-<version>.zipfile to the directory
<machine agent home>/monitors.
Run the following command after you have successfully downloaded the .zip file in the correct directory.
> unzip HanaDBMonitor-<VERSION>.zip -d <machine agent home>/monitors/
<machine agent home>/monitors/HanaDBMonitor/folder
config.yml. At minimum this is:
clusters: - connectionString: "jdbc:sap://<cluster1_host1>:<port>;<cluster1_host2>:<port>?communicationtimeout=20000" username: "" password: ""
mvn -DskipTests clean install
HanaDBMonitor-file can be found in the
|src/main/resources/config||Contains monitor.xml and config.yml|
|src/main/java||Contains source code to the HanaDB monitoring extension|
|target||Only obtained when using maven. Run 'maven clean install' to get the distributable .zip file.|
|pom.xml||maven build script to package the project (required only if changing Java code)|
Metrics can be configured in the
A reference for the HanaDB System Views can be found here
The Queries can be adjusted to your needs to gather metrics from the HanaDB. Please see below example:
queries: - statement: "select * from M_DISK_USAGE where USED_SIZE >= 0" columns: - name: "HOST" type: "name" - name: "USAGE_TYPE" type: "name" - name: "USED_SIZE" type: "metric" convertFrom: "" convertTo: "" - statement: "select HOST, USED_PHYSICAL_MEMORY, FREE_PHYSICAL_MEMORY from M_HOST_RESOURCE_UTILIZATION" columns: - name: "HOST" type: "name" - name: "USED_PHYSICAL_MEMORY" type: "metric" convertFrom: "" convertTo: "" - name: "FREE_PHYSICAL_MEMORY" type: "metric" convertFrom: "" convertTo: ""
Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.
Always feel free to fork and contribute any changes directly via GitHub.
config.yml: Validate the file here.
-Dappdynamics.agent.maxMetrics=5000if there is a metric limit reached error in the logs. If you don't see the expected metrics, this could be the cause.
The config cannot be nullerror: This usually happens when on a windows machine in
config.ymlfile path with linux file path separator
/. Use Windows file path separator
monitors\Monitor\config.yml. For Windows, please specify the complete path.
conf/logging/log4j.xmland update the level of the appender
com.singularityto debug. Let it run for 5-10 minutes and attach the logs to a support ticket.
[Read timed out]please check the
communicationtimeoutsetting within the
connectionString. The query and the processing time might not fit into the specified window.
For any questions or feature request, please contact AppDynamics Center of Excellence.