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

Labels names are considered semantically equivalent throughout the entire system #794

Open
johnaohara opened this issue Oct 23, 2023 · 1 comment
Labels
branch/master The master branch branch/stable The stable branch priority/hold An issuee that we need to look at - but later type/bug Something isn't working

Comments

@johnaohara
Copy link
Member

Labels are compared via their Name.

This means that all labels that have the same name are considered to be semantically equivalent across all Schemas . e.g. any Label name CPU Utilization could have different definitions. depending on the environment (i.e. bare-metal vs K8s) or collection tool (i.e. top vs prometheus).

The semantics of Labels are assumed to be the same across all users of the system, e.g. 'Time to first response' has the same definition for a web service vs an os bootstrap process.

Schemas are defined to process output from tools, and are designed to be shared across tests. Schemas support version evolution, but equivalence is considered based on the label name.

@johnaohara johnaohara added type/bug Something isn't working branch/master The master branch branch/stable The stable branch labels Oct 23, 2023
@johnaohara johnaohara added the priority/hold An issuee that we need to look at - but later label May 9, 2024
@johnaohara
Copy link
Member Author

On Hold due to #1603

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/master The master branch branch/stable The stable branch priority/hold An issuee that we need to look at - but later type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant