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: timestamp management between Kafka and NGSI-LD #492

Closed
wagmarcel opened this issue Jan 9, 2024 · 0 comments
Closed

BUG: timestamp management between Kafka and NGSI-LD #492

wagmarcel opened this issue Jan 9, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@wagmarcel
Copy link
Member

When samples enter through MQTT, they receive a Kafka timestamp. NGSI-LD has own timestamping methods like the system timestamps modifiedAt and createdAt. To align the timestamp concepts, the Kafka timestamp must be aligned with a NGSI-LD timestamp which can be set by API which is observedAt.

@wagmarcel wagmarcel added the bug Something isn't working label Jan 9, 2024
@wagmarcel wagmarcel added this to the API stable (beta) milestone Jan 9, 2024
@wagmarcel wagmarcel self-assigned this Jan 9, 2024
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Jan 9, 2024
Timestamp management was done so far by Kafka-timestamps. Every sample which entered the system throught MQTT-bridge is
automatically stamped by Kafka. This ensured that the timestamp cannot be manipulated by future values and, thus,
manipulating the system. The timestamp was stored in the TSDB but not explicitly in the NGSI-LD Database. This could lead to
unclear timestamp interpretations.
This PR makes timestamps more explicit by storing it also in the observedAt proerty in NGSI-LD.
In addition, this PR provides a first draft of JuPyter-Lab notebooks for experimenting with Flink-SQL. In the past this was
done by Apache Zeppelin but since there has not been any recent update the IFF Digital Twin team deciced to move
to JuPyter.

Related Issues: IndustryFusion#492

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Jan 9, 2024
Timestamp management was done so far by Kafka-timestamps. Every sample which entered the system throught MQTT-bridge is
automatically stamped by Kafka. This ensured that the timestamp cannot be manipulated by future values and, thus,
manipulating the system. The timestamp was stored in the TSDB but not explicitly in the NGSI-LD Database. This could lead to
unclear timestamp interpretations.
This PR makes timestamps more explicit by storing it also in the observedAt proerty in NGSI-LD.
In addition, this PR provides a first draft of JuPyter-Lab notebooks for experimenting with Flink-SQL. In the past this was
done by Apache Zeppelin but since there has not been any recent update the IFF Digital Twin team deciced to move
to JuPyter.

Related Issues: #492

Signed-off-by: marcel <[email protected]>
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