b97e8f3601
If a global vector-sink property on the logs plugin is set, we will use that to configure a log sink (defaulting to console output otherwise). Note that the actual configuration still needs to be a valid DSN representing a Vector log sink. While this does not support pinning log sinks to specific apps, it opens up integration for those who use a single k3s cluster in shared tenancy.
43 lines
798 B
YAML
43 lines
798 B
YAML
---
|
|
role: Agent
|
|
|
|
tolerations:
|
|
- effect: NoSchedule
|
|
key: node-role.kubernetes.io/master
|
|
operator: Exists
|
|
- effect: NoSchedule
|
|
key: node-role.kubernetes.io/infra
|
|
operator: Exists
|
|
|
|
service:
|
|
ports:
|
|
- name: prom-exporter
|
|
port: 9090
|
|
protocol: TCP
|
|
|
|
customConfig:
|
|
data_dir: /vector-data-dir
|
|
|
|
sources:
|
|
kubernetes_logs:
|
|
type: kubernetes_logs
|
|
|
|
transforms:
|
|
kubernetes_container_logs:
|
|
type: remap
|
|
inputs:
|
|
- kubernetes_logs
|
|
source: |
|
|
.message = .message
|
|
.container = .kubernetes.container_name
|
|
.pod = .kubernetes.pod_name
|
|
.namespace = .kubernetes.pod_namespace
|
|
|
|
sinks:
|
|
default_global_sink:
|
|
type: console
|
|
inputs:
|
|
- kubernetes_container_logs
|
|
encoding:
|
|
codec: json
|