ClusterCockpit/cc-specifications
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-specifications.git synced 2026-01-09 15:46:16 +01:00
Code Issues Packages Projects Releases Activity

Add root subject cc for NATS

Browse Source
This commit is contained in:
Jan Eitzinger
2025-12-23 09:20:12 +01:00
parent 4594c99395
commit 277bfa6c79
1 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
interfaces/lineprotocol/README.md
View File

@@ -31,9 +31,9 @@ There are four line-protocol message flavors:
- **Metric**: The `field` key is `value`, the `measurement` is the metric name
- **Event**: The `field` key is `event`. Events are actionable informations. The
`measurement` is set to an event class (job, slurm, status, phases, ?? ). Additional tag
`function` to indicate the purpose, similar to a REST endpoint (for the job
class this can be start_job and stop_job).
`measurement` is set to an event class (job, slurm, status, phases, ?? ).
Additional tag `function` to indicate the purpose, similar to a REST endpoint
(for the job class this can be start_job and stop_job).
- **Log**: The `field` key is `log`. Log messages are purely informational.
The `measurement` is set to the component identifier [ccb, ccms, ccmc, ccem,
ccnc]. Additional tag `loglevel` to set the log level (debug, info, warn,
@@ -50,7 +50,7 @@ types and easily filter the types an application is interested in the following
subject hierarchy tree is used:
```txt
<cluster name>. |
cc.<cluster name>. |
--- metrics
|
--- events.[job, slurm]