You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm experiencing inconsistent number of recorded readings for the asset when running Fledge (Fledge power version) with a custom South Python-based plugin. Fledge is configured with the following storage setup:
Fledge Power version: 2.4.0 and 2.4.0-141(nightly build)
Storage plugin: PostgreSQL
Readings plugin: SQLMemory
South plugin: Python based RabbitMQ client
During testing, I stream approximately 900 datapoints per second to the plugin in one batch, calling:
Note: The message returns the counter per asset, but not for the entire service. The value displayed by the UI is unclear.
GET /fledge/statistics:
The same results are shown, with 599 updates received for each asset.
GET /fledge/asset (Asset tab in GUI):
Indicates 119 to 120 updates per asset. Observing this parameter during the test, I noticed that around 450 updates, it rolls over to stats from a lower value (possibly starting from zero).
Question:
Why is there a inconsistent update count shown in the asset tab?
The text was updated successfully, but these errors were encountered:
kwitekrac
changed the title
inconsistent number of recorded readings for the asset (GET /fledge/asset or the asset tab inUI)
inconsistent number of recorded readings for the asset (GET /fledge/asset or the asset tab in the UI)
Jun 26, 2024
Description:
I'm experiencing inconsistent
number of recorded readings for the asset
when running Fledge (Fledge power version) with a custom South Python-based plugin. Fledge is configured with the following storage setup:Fledge Power version: 2.4.0 and 2.4.0-141(nightly build)
Storage plugin: PostgreSQL
Readings plugin: SQLMemory
South plugin: Python based RabbitMQ client
During testing, I stream approximately 900 datapoints per second to the plugin in one batch, calling:
where ingest_elements contains around 900 elements.
Actual Behavior:
After running the test, I checked the following metrics:
GET /fledge/south requests (South tab in GUI):
The number of updates indicated is 599:
Note: The message returns the counter per asset, but not for the entire service. The value displayed by the UI is unclear.
GET /fledge/statistics:
The same results are shown, with 599 updates received for each asset.
GET /fledge/asset (Asset tab in GUI):
Indicates 119 to 120 updates per asset. Observing this parameter during the test, I noticed that around 450 updates, it rolls over to stats from a lower value (possibly starting from zero).
Question:
Why is there a inconsistent update count shown in the asset tab?
The text was updated successfully, but these errors were encountered: