-
Notifications
You must be signed in to change notification settings - Fork 88
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
Fiware IoT Agent json is changing the service path of incoming messages if it is high load #750
Comments
@pratappulugoru both iotagent and iota-node-lib are quite old, You should try with newer versions of iota where that issues where addressed. |
@pratappulugoru since many versions ago (you can see full doc in https://github.com/telefonicaid/iotagent-json/blob/master/docs/usermanual.md#mqtt-binding) measures are sent on the |
@AlvaroVega Thanks for the update. I will try with the latest version. Can you help me in understanding how Iot Agent can switch the service provider automatically. Is their any bug and fixed in latest versions. But i have not seen any thing like this in the release notes of latest versions. |
I have no previous info about an iotagent can switch the service provider automatically, just some bugs related about logs (context domains) were printing service/subservice in a wrong way. |
@pratappulugoru can you confirm you are receiving entities updates with a different fiware-service (I mean, if you have a context broker, there are entities created in the Context Broker, not only log outputs)? |
Yes, we have recieved the entities with different service paths. Our probelm is if we are using multiple service path's then we are observing that only some requests are throwing Socket errors and those requests did not reach to Orion.- But all successfull messages reached to orion with different service path's also. |
@pratappulugoru did you tried with latest iotagent version? |
@AlvaroVega Not yet. We are planning to do in this week. I will let you know the results once test is done. I have recorded this issue in Orion. |
It's very strange, neither old or newer versions we reproduce the problems your describe. Anyway, if you can provide any other detail, PoC, testCase or way for fully reproduce it we will appreciate it. |
@AlvaroVega can you go thorough the below link |
@pratappulugoru telefonicaid/iotagent-ul#383 is about services/subservices showed in logs, not received in CB entities. IMHO is not the same. |
Could you please share a step by step guide to reproduce it? This means:
If you do not provide this, it would be impossible for us to reproduce the issue and give you support. Thanks in advance |
@AlvaroVega we have upgraded the iotagent and orion to the latest version. But still we are seeing the service provider mismatch in the logs. Its consistent issue. We are observing from last six months. Can you please help here?. For single service path, its works fine. |
Hi @pratapmai,
Where is the script that you use to ingest measures for different service path?
Thank in advance
|
IoT Agent JSON version the issue has been seen with
1.20
Bound or port used (API interaction)
Northbound (Provision API and NGSI Interactions)
NGSI version
NGSIv2
Are you running a container?
Yes, I am using a contaner (Docker, Kubernetes...)
Image type
normal
Expected behaviour you didn't see
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.18.0 version.
iotagent-json 1.20.0 version.
Orion - 3.4.0 version.
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Configs
Log output
No response
The text was updated successfully, but these errors were encountered: