-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Labels
bugSomething isn't workingSomething isn't workingprocessor/k8sattributesk8s Attributes processork8s Attributes processor
Description
Component(s)
processor/k8sattributes
What happened?
Description
When the agent is first started, the k8s metadata has not been fully synchronized by the k8sattributes processor. If any data passes through the component at this point, they will not be associated with metadata.
Steps to Reproduce
- start a service that continuously sends a large amount of data to the agent.
- (re)start the agent.
Expected Result
All data should be associated with k8s metadata.
Actual Result
There may be a little data that hasn't be assosicated.
Collector version
v0.95.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
I think it's the best solution to wait for an initial sync when starting k8sattributes processor.
Or we can block data util an initial sync is finished.
dfroberg, Qbandev, orloffv and stuart23
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingprocessor/k8sattributesk8s Attributes processork8s Attributes processor