Internal logs
Expose all log and trace messages emitted by the running Vector instance
Configuration
Example configurations
{
"sources": {
"my_source_id": {
"type": "internal_logs"
}
}
}
[sources.my_source_id]
type = "internal_logs"
sources:
my_source_id:
type: internal_logs
{
"sources": {
"my_source_id": {
"type": "internal_logs",
"host_key": "host",
"pid_key": "pid"
}
}
}
[sources.my_source_id]
type = "internal_logs"
host_key = "host"
pid_key = "pid"
sources:
my_source_id:
type: internal_logs
host_key: host
pid_key: pid
host_key
optional string literalOverrides the name of the log field used to add the current hostname to each event.
By default, the global log_schema.host_key
option is used.
Set to ""
to suppress this key.
host
pid_key
optional string literalOverrides the name of the log field used to add the current process ID to each event.
By default, "pid"
is used.
Set to ""
to suppress this key.
pid
Outputs
<component_id>
Output Data
Logs
Warning
Line
gethostname
command.my-host.local
Vector has started.
4232
internal_logs
2020-10-10T17:07:36.452332Z
Telemetry
Metrics
linkcomponent_discarded_events_total
countercomponent_id
instead. The value is the same as component_id
.filter
transform, or false if due to an error.component_errors_total
countercomponent_id
instead. The value is the same as component_id
.component_received_bytes_total
countercomponent_id
instead. The value is the same as component_id
.component_received_event_bytes_total
countercomponent_id
instead. The value is the same as component_id
.component_received_events_count
histogramA histogram of the number of events passed in each internal batch in Vector’s internal topology.
Note that this is separate than sink-level batching. It is mostly useful for low level debugging performance issues in Vector due to small internal batches.
component_id
instead. The value is the same as component_id
.component_received_events_total
countercomponent_id
instead. The value is the same as component_id
.component_sent_event_bytes_total
countercomponent_id
instead. The value is the same as component_id
.component_sent_events_total
countercomponent_id
instead. The value is the same as component_id
.source_lag_time_seconds
histogramcomponent_id
instead. The value is the same as component_id
.How it works
Logs are limited by startup options
VECTOR_LOG
environment variable and the --quiet
and --verbose
command-line options. The internal_logs
source only receives logs that are generated by these options.