What product/components do you use and which version/fix level are you on?
Latest
Is your question related to the free trial, or to a production (customer) instance?
Production
What are you trying to achieve? Please describe it in detail.
The events counter model has not processed bulk input events.
Below is the screenshot of the model.
The configuration of event input block is the “New events” and the ignore timestamp.
The IoT device has sent bulk of events to the stream analytics model. The time difference between the real time events happend and ingestion time is 3 hours.
Do you get any error messages? Please provide a full error message screenshot and log file.
Have you installed all the latest fixes for the products and systems you are using?
The iot edge gateway saves the events on the device when there is no internet connection. The unpublished events are sent to the cloud one by one through thinedge mqtt topic when the internet connection comes back.
The events are generated at 15:19:49 but uploaded at 18:21:30 to the cloud through thinedge.io.
The above stream analytics model is unable to take this input for computation.
Can you reproduce the problem, then provide an enhanced diagnostics zip (so it will contain information relevant to the error/anomaly if any)? There’s a link called ‘Enhanced’ at the bottom of the screen that will do the download for you.
From your initial description, it sounded like “Ignore Timestamp” was enabled. I loaded you model and it is actually disabled. Can you please re-test with “Ignore Timestamp” enabled?
It’s configuring when an event will actually be received by the input block (and sent into the model).
In the Cumulocity IoT data model, an event can be modified in place, not just created. If an event is modified in place, then ‘Updates Only’ or ‘All’ will send that event with its latest state into the model each time it’s modified. With ‘New events only’ or ‘All’ you will also get newly created events going into the model.
creationTime is the time when the object has been initially created in the database.
`lastUpdated? is the time when the object has been last updated.
For events the time is used to reorder the events. When selecting ignore Timestamp the events are not re-ordered and will be processed as occurred in the platform.
In your case when not checked: an event has been processed which has a newer timestamp time so any other event with an older timestamp, even occured later, will be ignored. When checked you get this event, no matter if the time is in the past or future.
