Attributes
You may want to see what a team or a department spent, not only what a project cost. An attribute is on a person, such as team: web or department: engineering. It says who the person is; a tag says what the work was for. The two words are different on purpose.
Attribute values
Like tag values, attribute values are records with a key, an optional title and default attributes. Built in: team, department, location. An org manager adds names.
| Attribute | Example value | Default attributes |
|---|---|---|
team |
web |
department: engineering |
department |
engineering |
None |
location |
vienna |
None |
A person has at most one value per attribute name. Someone in two teams picks a main one, or the organization adds a second attribute name such as guild. There is no team tree: defaults do it, so cost per department is the sum of its teams without any tree.
On messages
A message carries its person's attributes as of its time. An attribute value on a person has a from date, so a team change on 1 April leaves March on the old team at every as-of date, and April on the new one.
In filters
Attributes and tags mix in one filter: cost of team: web on client: acme, the plan of department: engineering, a grant on team: web. A head of engineering is a people manager over department: engineering; a role is never a tag or an attribute.
OTEL_RESOURCE_ATTRIBUTES can send team=web with every message. That arrives as a signal, not as the attribute. A rule may read it to set a tag. A person's attributes are set on the person, from a date.