I'm developing a service that runs alongside my Scorpio NGSI-LD broker and other databases. This service exposes an API that allows users to update entities, and these updates are propagated to Scorpio. Conversely, I also want changes made directly via Scorpio to be reflected in my service.
To achieve this, I created a normalized subscription in Scorpio with the trigger set to entityUpdate, listening to all entity types ("type": "*"). I've also created entityCreated and entityDeleted subscriptions.
The issue I'm facing is that Scorpio does not provide a mechanism to identify which updates originated from my service—so when Scorpio echoes back the update through the subscription notification, I can't distinguish it from updates made externally.
Is there a way to address this, such as tagging requests or filtering self-originated updates?