[Backlogmanager] [FIWARE-JIRA] (HELP-22182) [fiware-stackoverflow] Fiware IoT Agent is changing the service path of incoming message

[José Ignacio Carretero Guarde (JIRA)]

     [ https://jira.fiware.org/browse/HELP-22182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

José Ignacio Carretero Guarde deleted HELP-22182:
-------------------------------------------------


> [fiware-stackoverflow] Fiware IoT Agent is changing the service path of incoming message
> ----------------------------------------------------------------------------------------
>
>                 Key: HELP-22182
>                 URL: https://jira.fiware.org/browse/HELP-22182
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>              Labels: fiware, fiware-orion, iot
>
> Created question in FIWARE Q/A platform on 13-09-2023 at 20:09
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/77100168/fiware-iot-agent-is-changing-the-service-path-of-incoming-message
> +Question:+
> Fiware IoT Agent is changing the service path of incoming message
> +Description:+
> We are currently using the VernemQ MQTT server in conjunction with a Fiware stack that comprises the IoT Agent and Orion Context Broker. When sending data to the IoT Agent, we utilize the message topic format api-key/device-id/attrs.
> When the IoT Agent receives a message on this topic, it uses the provided 'api-key' to determine both the service path and service name. Once these values are determined, the payload is then forwarded to the Orion Context Broker using the v2/entities/ API.
> Our setup works perfectly when the data rate is relatively low, around 40,000 records per hour. However, when the data rate increases to approximately 80,000 records per hour, we've noticed that the IoT Agent appears to change the service provider from, for example, 'serviceProvider1' to 'serviceProviderXy'.
> We're currently at a loss as to why this change is occurring, and it is causing significant security concerns for our system. We would greatly appreciate any insights or assistance in understanding and resolving this issue.
> We tried running multiple tests with higher data rate(>=80k records per hour)  and observed in all the tests this phenomenon is common. When we run tests with lesser data rate, this is not occuring.
> iotagent-node-lib - 2.12.0 version.
> iotagent-json 1.14.0 version.
> Orion - 2.4.0 version.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)