Skip to content

Some data couldn't be associated with k8s metadata when the agent was just started. #32556

@h0cheung

Description

@h0cheung

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions