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.

Sign up for GitHub

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

Jump to bottom

Begin emitting entity events (as logs) from k8scluster receiver #24400

Closed
Tracked by #19741
tigrannajaryan opened this issue Jul 19, 2023 · 1 comment · Fixed by #24419
Closed
Tracked by #19741

Begin emitting entity events (as logs) from k8scluster receiver #24400

tigrannajaryan opened this issue Jul 19, 2023 · 1 comment · Fixed by #24419
Assignees
@tigrannajaryan
Labels
receiver/k8scluster

Comments

@tigrannajaryan
Copy link
Member

No description provided.

@tigrannajaryan tigrannajaryan mentioned this issue Jul 19, 2023
Open
10 tasks
@tigrannajaryan tigrannajaryan self-assigned this Jul 19, 2023
@tigrannajaryan tigrannajaryan mentioned this issue Jul 20, 2023
Merged
tigrannajaryan added a commit to tigrannajaryan/opentelemetry-collector-contrib that referenced this issue Jul 20, 2023
@tigrannajaryan
[receiver/k8sclusterreceiver] Begin emitting entity events as logs
2daab45 
Resolves open-telemetry#24400

This is part 3 of the work to move to entity events-as-log-records in K8s cluster receiver:
open-telemetry#19741

Overall design document:
https://docs.google.com/document/d/1Tg18sIck3Nakxtd3TFFcIjrmRO_0GLMdHXylVqBQmJA/

Example log record emitted when a pod changes:
```
ObservedTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 1970-01-01 00:00:00 +0000 UTC
SeverityText:
SeverityNumber: Unspecified(0)
Body: Empty()
Attributes:
     -> otel.entity.id: Map({"k8s.pod.uid":"07cc87d9-8e76-4472-b5ee-c9ecbad94ea9"})
     -> otel.entity.event.type: Str(entity_state)
     -> otel.entity.type: Str(k8s.pod)
     -> otel.entity.attributes: Map({"k8s-app":"kubernetes-dashboard","k8s.deployment.name":"kubernetes-dashboard","k8s.deployment.uid":"4c1ee765-906b-498b-80b5-bea67a714fce","k8s.replicaset.name":"kubernetes-dashboard-6c7ccbcf87","k8s.replicasetuid":"e8c052b4-c1db-43bd-806d-f85d8a861f5b","k8s.service.kubernetes-dashboard":"","k8s.workload.kind":"Deployment","k8s.workload.name":"kubernetes-dashboard","pod-template-hash":"6c7ccbcf87","podcreation_timestamp":"2023-06-30T11:32:00-04:00"})
Trace ID:
Span ID:
Flags: 0
```
@github-actions
Copy link
Contributor

Pinging code owners for receiver/k8scluster: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

dmitryax pushed a commit that referenced this issue Jul 21, 2023
@tigrannajaryan
[receiver/k8sclusterreceiver] Begin emitting entity events as logs (#…
1c36f05 
…24419)

Resolves
#24400

This is part 3 of the work to move to entity events-as-log-records in
K8s cluster receiver:

#19741

Overall design document: 

https://docs.google.com/document/d/1Tg18sIck3Nakxtd3TFFcIjrmRO_0GLMdHXylVqBQmJA/

Example log record emitted when a pod changes:
```
ObservedTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 1970-01-01 00:00:00 +0000 UTC
SeverityText:
SeverityNumber: Unspecified(0)
Body: Empty()
Attributes:
     -> otel.entity.id: Map({"k8s.pod.uid":"07cc87d9-8e76-4472-b5ee-c9ecbad94ea9"})
     -> otel.entity.event.type: Str(entity_state)
     -> otel.entity.type: Str(k8s.pod)
     -> otel.entity.attributes: Map({"k8s-app":"kubernetes-dashboard","k8s.deployment.name":"kubernetes-dashboard","k8s.deployment.uid":"4c1ee765-906b-498b-80b5-bea67a714fce","k8s.replicaset.name":"kubernetes-dashboard-6c7ccbcf87","k8s.replicasetuid":"e8c052b4-c1db-43bd-806d-f85d8a861f5b","k8s.service.kubernetes-dashboard":"","k8s.workload.kind":"Deployment","k8s.workload.name":"kubernetes-dashboard","pod-template-hash":"6c7ccbcf87","podcreation_timestamp":"2023-06-30T11:32:00-04:00"})
Trace ID:
Span ID:
Flags: 0
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tigrannajaryan tigrannajaryan

Labels
receiver/k8scluster
Projects
None yet
Milestone
No milestone
1 participant
@tigrannajaryan