We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Specific example: In a multi-zonal cluster, k8s.cluster and k8s.node entities can both have cloud.availability_zone attribute with different values.
k8s.cluster
k8s.node
cloud.availability_zone
The problem described in more detail in https://docs.google.com/document/d/1sUwKJEwPB89uA1jUrX6ea-w-mIYNk5TJ8NuMOAZfW2M/edit?tab=t.0 by @quentinmit.
We discussed this problem as part of Additional requirements for entities data model during Entities SIG meeting on Jan 16 and agreed on a solution that is closer to what's described as potential solution A in https://docs.google.com/document/d/1sUwKJEwPB89uA1jUrX6ea-w-mIYNk5TJ8NuMOAZfW2M/edit?tab=t.0#heading=h.ezgpqjbuutx8.
cc @tigrannajaryan
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Specific example: In a multi-zonal cluster,
k8s.cluster
andk8s.node
entities can both havecloud.availability_zone
attribute with different values.The problem described in more detail in https://docs.google.com/document/d/1sUwKJEwPB89uA1jUrX6ea-w-mIYNk5TJ8NuMOAZfW2M/edit?tab=t.0 by @quentinmit.
We discussed this problem as part of Additional requirements for entities data model during Entities SIG meeting on Jan 16 and agreed on a solution that is closer to what's described as potential solution A in https://docs.google.com/document/d/1sUwKJEwPB89uA1jUrX6ea-w-mIYNk5TJ8NuMOAZfW2M/edit?tab=t.0#heading=h.ezgpqjbuutx8.
cc @tigrannajaryan
The text was updated successfully, but these errors were encountered: