Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Otel collector reading old logs after migration from SCK #564

Closed
ghost opened this issue Oct 19, 2022 · 0 comments · Fixed by #567
Closed

Otel collector reading old logs after migration from SCK #564

ghost opened this issue Oct 19, 2022 · 0 comments · Fixed by #567
Assignees
Labels
Splunk Platform Issue related to Splunk Platform destination

Comments

@ghost
Copy link

ghost commented Oct 19, 2022

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"
`

@atoulme atoulme added the Splunk Platform Issue related to Splunk Platform destination label Oct 19, 2022
@hvaghani221 hvaghani221 self-assigned this Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Splunk Platform Issue related to Splunk Platform destination
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants