Log Level
The log_level
setting designates custom log levels for the services in a Hydrolix cluster.
Specify a YAML dictionary with hydrolix service names or the wildcard string “*”
as keys. Service name keys take precedence over the default wildcard key.
The example below sets all services that respect this setting to the info
level except for stream-head
and query-head
, which are set to use the critical
and trace
setting, respectively:
log_level:
"*": info
stream-head: critical
query-head: trace
Valid log level values:
critical
error
warning
info
debug
trace
Values are case-insensitive.
Below is a list of services that support the log_level
setting. Services not on this list ignore this setting.
akamai-siem-indexer
akamai-siem-peer
alter
alter-head
alter-indexer
autoingest
batch-head
batch-indexer
batch-peer
decay
intake-api
intake-head
job-purge
kafka-indexer
kafka-peer
kinesis-indexer
kinesis-peer
log-vacuum
merge
merge-cleanup
merge-controller
merge-head
merge-indexer
merge-peer
partition-vacuum
prune-locks
query-head
query-peer
reaper
rejects-vacuum
stale-job-monitor
stream-head
stream-indexer
stream-peer
summary_peer
summary-indexer
task-monitor
turbine-api
validator
validator-indexer
Updated 6 months ago