You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even migrationcheckpoint initContainer seems to ran successful Otel collector is reading log files from beginning. That makes a huge pressure on Splunk due to a high events rate just right after Otel collector starts. I'm migrating from SCK 1.4.15 to Otel 0.61.1.
Hi,
Even migrationcheckpoint initContainer seems to ran successful Otel collector is reading log files from beginning. That makes a huge pressure on Splunk due to a high events rate just right after Otel collector starts. I'm migrating from SCK 1.4.15 to Otel 0.61.1.
splunk-otel-collector helm values.yaml file:
`---
splunkPlatform:
metricsEnabled: false
fieldNameConvention:
renameFieldsSck: true
keepOtelConvention: false
logsEngine: otel
journald:
enabled: false
agent:
resources:
requests:
cpu: 200m
memory: 500Mi
limits:
cpu: 4
memory: 6Gi
podAnnotations:
platform/scrape: "true"
platform/scrape_port: "8889"
`
The text was updated successfully, but these errors were encountered: