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

[DOC] Add to special measure name metadata key #1634

Open
mapedraza opened this issue Aug 6, 2024 · 1 comment
Open

[DOC] Add to special measure name metadata key #1634

mapedraza opened this issue Aug 6, 2024 · 1 comment

Comments

@mapedraza
Copy link
Collaborator

mapedraza commented Aug 6, 2024

## Special measures and attributes names
In case of arriving measures with name `id` or `type`, they are automatically transformed to `measure_id` and
`measure_type` attributes at Context Broker update. The reason behind this is to avoid to collide with the original
entity ID and type, as mechanism that enable store measure values from parameters called with the same name. It only
applies to autoprovisioned attributes and is also available at JEXL context with the same name (`measure_id` or
`measure_type`).
In case of provisioning attributes using `id` or `type` as names (please don't do that ;), they are ignored.

EDIT:

Add also metadata here:

The agent provides additional information, hereafter referred as **context**, in order to be used to evaluate the
expression. In all cases the following data is available to all expressions:
- `id`: device ID
- `entity_name`: NGSI entity Name (principal)
- `type`: NGSI entity type (principal)
- `service`: device service
- `subservice`: device subservice
- `staticAttributes`: static attributes defined in the device or config group

@AlvaroVega
Copy link
Member

done in #1641. Should we close this?

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

No branches or pull requests

2 participants