hbase.yaml #459
hbase.yaml #459
Conversation
For the HBase database I needed a config file. Found one here https://blog.godatadriven.com/hbase-prometheus-monitoring but it could not handle _ in table names.
| namespace: "$1" | ||
| table: "$2" | ||
| region: "$3" | ||
| value: "$5" |
There was a problem hiding this comment.
Why are you not leaving this to the default?
| # Idea came from https://blog.godatadriven.com/hbase-prometheus-monitoring | ||
| rules: | ||
| - pattern: Hadoop<service=HBase, name=RegionServer, sub=Regions><>Namespace_(.+)_table_(.+)_region_(.+)_metric_(.+):\ (.+) | ||
| name: HBase_metric_$4 |
There was a problem hiding this comment.
metric is redundant here
we also go with lowercase, so hbase
There was a problem hiding this comment.
It may be added so that it does not overwrite other metrics which may overlap or have different type.
for example in HBase you can have already generated metric named Hbase_active: 1.0
Then there is some hbase data with below structure (abbreviated)
...Namespace_test_table_meta_region_abc_metric_get: 20
and which would produce Hbase_active with labels namespace=test,table=meta,region=abc with value 20.0
In that case it would cause metric clash.
I would keep lowercase, as suggested.
| @@ -0,0 +1,13 @@ | |||
| # The metrics look this this | |||
| # Hadoop<service=HBase, name=RegionServer, sub=Regions><>Namespace_foo_table_my_table_name_region_1234567xy_metric_scanNext_75th_percentile: 0.0 | |||
| # So we have many many different metrics and it is hard to aggregate per namespace or per table | |||
There was a problem hiding this comment.
No need for this comment, this is the usual way to do things.
For the HBase database I needed a config file. Found one here https://blog.godatadriven.com/hbase-prometheus-monitoring but it could not handle _ in table names.