mirror of
https://github.com/zeek/zeek.git
synced 2025-10-01 22:28:20 +00:00
telemetry: Rename endpoint label to node label
Using a label named "endpoint" is not intuitive and requires explaining to users that it's really just the Cluster::node value. Change the label to "node", so that we don't need to do the explaining. This probably breaks some existing users of the Prometheus metrics, but after looking more at metrics recently, "endpoint" really is a thorn in my eye.
This commit is contained in:
parent
8189716adc
commit
eea194ddd8
7 changed files with 41 additions and 19 deletions
12
NEWS
12
NEWS
|
@ -48,6 +48,18 @@ Breaking Changes
|
|||
|
||||
redef EventMetadata::add_missing_remote_network_timestamp = T;
|
||||
|
||||
- The "endpoint" label of metrics exposed via Prometheus or the ``telemetry.log``
|
||||
was renamed to "node". This is done for consistency with cluster terminology:
|
||||
The label values have always been the value of ``Cluster::node`, so it's more intuitive
|
||||
to call it. The "endpoint" name originated from a time when the telemetry framework
|
||||
was implemented in Broker.
|
||||
|
||||
To revert to the "endpoint" label, you can do the following, but we strongly
|
||||
suggest to migrate to the new default "node" instead:
|
||||
|
||||
redef Telemetry::metrics_endpoint_label = "endpoint";
|
||||
|
||||
|
||||
New Functionality
|
||||
-----------------
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue