Mirror/zeek
1
0
Fork 0
mirror of https://github.com/zeek/zeek.git synced 2025-10-02 06:38:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Comment-only tweaks for telemetry-related settings.

Browse source 
These weren't quite accurate any more.
This commit is contained in:
Christian Kreibich 2024-07-04 15:20:42 -07:00
parent 4d31335391
commit 3ecacf4f50
3 changed files with 3 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
scripts/base/frameworks/telemetry/options.zeek
View file

@ -11,7 +11,7 @@ export {
const metrics_address = getenv("ZEEK_DEFAULT_LISTEN_ADDRESS") &redef;
## Port used to make metric data available to Prometheus scrapers via
## HTTP.
## HTTP. The default value means Zeek won't expose the port.
const metrics_port = 0/unknown &redef;
## ID for the metrics exporter. This is used as the 'endpoint' label

4
scripts/policy/frameworks/telemetry/prometheus.zeek
View file

@ -2,10 +2,6 @@
##! from the cluster node configuration for exporting data to
##! Prometheus.
##!
##! For customization or disabling, redef the involved Telemetry options
##! again. Specifically, to disable listening on port 9911, set
##! :zeek:see:`Telemetry::metrics_port` to `0/unknown` again.
##!
##! The manager node will also provide a ``/services.json`` endpoint
##! for the HTTP Service Discovery system in Prometheus to use for
##! configuration. This endpoint will include information for all of

4
scripts/site/local.zeek
View file

@ -94,8 +94,8 @@ redef digest_salt = "Please change this value.";
# telemetry_histogram.log.
@load frameworks/telemetry/log
# Enable metrics centralization on the manager. This opens port 9911/tcp
# on the manager node that can be readily scraped by Prometheus.
# Enable Prometheus metrics scraping in the cluster: each Zeek node will listen
# on the metrics port defined in its Cluster::nodes entry.
# @load frameworks/telemetry/prometheus
# Uncomment the following line to enable detection of the heartbleed attack. Enabling