ClusterCockpit/cc-specifications
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-specifications.git synced 2024-11-10 01:37:25 +01:00
Code Issues Packages Projects Releases Activity

Update interfaces/lineprotocol README.md

Browse Source
This commit is contained in:
Thomas Gruber 2023-10-05 14:37:32 +02:00 committed by GitHub
parent f0bccc8229
commit aafbc28895
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
interfaces/lineprotocol/README.md
View File

@ -23,7 +23,7 @@ Each metric is identifiable by the `measurement` (= metric name), the `hostname`
## Mandatory fields per measurement: ## Mandatory fields per measurement:
The field key is always `value`. No other field keys are evaluated by the ClusterCockpit ecosystem. The field key is always `value`. No other field keys are evaluated by the ClusterCockpit ecosystem.
## Optional tags depending on the measurment: ## Optional tags depending on the measurement:
In some cases, optional tags are required like `filesystem`, `device` or `version`. While you are free to do that, the ClusterCockpit components in the stack above will recognize `stype` (= sub type) and `stype-id` in the future. So `filesystem=/homes` should be better specified as `stype=filesystem,stype-id=/homes` In some cases, optional tags are required like `filesystem`, `device` or `version`. While you are free to do that, the ClusterCockpit components in the stack above will recognize `stype` (= sub type) and `stype-id` in the future. So `filesystem=/homes` should be better specified as `stype=filesystem,stype-id=/homes`