THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
In addition to the Counter & Timer metrics collected from EclipseLink, a computed metric of Timer/Counter (divided by) is also sent. This metrics provides the average time taken for an operation across time.
For example, if
Counter Metric : Counter.ReadAllQuery.HostRoleCommandEntity = 10000
Timer Metric : Timer.ReadAllQuery.HostRoleCommandEntity = 50
Computed Metric (Avg time for the operation) : ReadAllQuery.HostRoleCommandEntity = 200 (10000 div by 50)
As seen above, the computed metric name will be the same as the Timer & Counter metric except without the 'Timer.' / 'Counter.' prefix.
To enable this source, add "database" to the metric.sources config in metrics.properties and restart Ambari Server.
Configs
Ambari performance monitor granularity : NONE / NORMAL / HEAVY / ALL
| Config Name | Default Value | Explanation |
|---|---|---|
source.database.class | org.apache.ambari.server.metrics.system.impl.DatabaseMetricsSource | Class used to collect Database Metrics from extended Performance Monitor class - org.apache.ambari.server.metrics.system.impl.AmbariPerformanceMonitor. |
source.database.performance.monitor.query.weight | HEAVY | |
source.database.monitor.dumptime | ||
source.database.monitor.entities | ||
source.database.monitor.query.keywords.include |
Grafana dashboards
Disabling Ambari Server metrics globally
...