Had a quick question around the API GET for Channel Events (“/api/5.1/channels/events”), how long are the events shown in this command stored within MCS? I would like to run a script to scrape the events every x amount of minutes and want to ensure I’m using a suitable threshold of minutes that I won’t miss any events but also I am not sending too many unnecessary API calls.
Just to confirm - you’re pointing the API to MCS, not MCM, yes?
MCM can store events for a very short period of time.
MCS can hold it for longer, the time range limit is dictated by the amount of storage you’ve dedicated to the Elastic search DB that stores all this historical data.
Storage consumption of the Elastic search DB is about 25GB per day for every 100 monitored channels.
Note that you can use API GET, but another useful way could be to direct the data flow to another DB like Kafka, Splunk etc’ and manage it from there.
Thanks Nir for confirming how the calculation works.
Was able to perform some tests during a quiet period and a busy period and find a good balance for how often to poll based on our configuration.
End goal is obviously to get to a place where we can implement the Kafka implementation but we just aren’t at a point yet of being able to implement so the API GET is a starter point for us for now.