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

🐛 [BUG] - cluster_name tag don't generate k8s.deployment.name #49

Open
dimitrisfinas opened this issue May 11, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@dimitrisfinas
Copy link

Description

When you use the tag "cluster_name" to generate your k8s cluster resource attributes:

  • it generates an empty value for k8s.deployment.name. Could it generate a value equal to your service name?
  • it doesn't generate any k8s.replicaset.name, even if you use pod_count. Can you generate it in this case?
  • it doesn't generate any k8s.node.name or k8s.node.uid. can you generate it also?
  • a k8s.namespace.name is generated with the name of the service, could it be possible to override this value with an attribute with same name that we will set in resourceAttrs?

BTW, it will be great to be able to override any generated key/value by simply putting the same key with your own value in the resourceAttrs list.
Thanks

Reproduction URL

https://github.com/dimitrisfinas/telemetry-generator/blob/main/examples/ebank.yaml

Reproduction steps

1. Create your own scenario
2. Add a kubernetes: cluster_name: in your ressourceAtttrSets:
3. See traces obtained and look at resource attributes
4. See error

Screenshots

No response

Logs

No response

Browsers

No response

OS

No response

@dimitrisfinas dimitrisfinas added the bug Something isn't working label May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant