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

Processes: mess with target_info's instance attribute (OTEL export) #1124

Closed
mariomac opened this issue Sep 2, 2024 · 0 comments · Fixed by #1129
Closed

Processes: mess with target_info's instance attribute (OTEL export) #1124

mariomac opened this issue Sep 2, 2024 · 0 comments · Fixed by #1129
Assignees

Comments

@mariomac
Copy link
Contributor

mariomac commented Sep 2, 2024

Process dashboards show the following error:

Image

Causes:

  • Dashboard needs to join process metrics and target_info
  • only one instance of target_info is allowed for each instance attribute
  • however, Beyla can create two target_info for the same resource:
    1. when Beyla receives process metrics before it gets the Kubernetes metadata, creates a target_info
    2. when Beyla receives the K8s metadata, creates a new target_info for the same instance ID, but with different attributes

Captures of a query for a given target_info following a given instanceID

Image

Image

Observe that there are also two target_info entries that do not show any process resource information. This means that another duplicity is added: target-info of applications and target-info of processes.

@mariomac mariomac added the bug label Sep 2, 2024
@mariomac mariomac changed the title Mess with target_info's instance attribute (OTEL export) Processes: mess with target_info's instance attribute (OTEL export) Sep 2, 2024
@mariomac mariomac self-assigned this Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant