What do I do if my Restream Queue is getting full?
First of all, don’t worry, your Restream Queue is monitored to ensure you are notified if it is starting to fill up beyond a certain threshold. This could be caused by importing a new source with a high volume of data and not mapping these fields to a table in your data warehouse, for example. Another potential reason events are sent to the Restream Queue is if a data warehouse table was deleted or Alooma cannot connect.
Although unlikely, if you still do not have a chance to address any of our emails, phone calls, IMs, or smoke signals and the Restream Queue does fill to capacity, any further events will be discarded. However, if S3 retention is enabled, you can still recover your raw events and there will be no data loss.
How do I know what's in my Restream Queue?
Currently the only way to know what's in the Restream Queue is to look through the notifications. The notification pane only shows the last 24 hours of notifications, so if you'd like to see notifications that were emitted as a result of older events, restream the events in the Restream Queue and they will pop back up.
If you're having trouble navigating the contents of the Restream Queue, feel free to contact us.
What do I do if I don't care about the events in my Restream Queue?
We get it, not all events are created equal and not all must reach your data warehouse. You have a few options:
- If there's a set of events which you want to clear out of the Restream Queue, add code to the Code Engine that identifies them by some attribute and then discards them. Then, restream. Note that newly arriving events with that attribute will also be discarded.
- If you don't care about any of the events currently in the Restream Queue, because you've addressed the events in there that you do care about, you can click the restream button and then choose the Purge Restream option. Note this is a destructive operation and will permanently delete all events from the restream queue.