Export API - Bitmovin Analytics

Hi,
Our questions are regarding Export API.
Export [API] - (Bitmovin Docs - Analytics Tutorials | How to Export Bitmovin Analytics Data)

  • Are there any limitations in the POST Export API that we need to know? Eg: Time period (can we expect all fields for the last three months), Fields available: are all the fields available with the POST impression API available here too.
  • Can we use any other cloud service provider apart from AWS/Azure/GCS? Since we currently have our entire infra on Oracle Cloud?
  • Under the output key for the POST Exports API request body, there is confusion as to what value is expected in the outputId field. Is this any custom id that we can provide it with (as understood by the term <YOUR_OUTPUT_ID> used in the examples, or is it a value to be obtained from another API response and used here? (as understood by “A configuration that holds the ID of an existing Analytics Output”)
2 Likes

Hi @billpay

thanks for the questions.

  • Are there any limitations in the POST Export API that we need to know? Eg: Time period (can we expect all fields for the last three months), Fields available: are all the fields available with the POST impression API available here too.

The POST Export API contains all the raw data that we collect from clients so it is absolutely the API you are looking for. All the fields are available and there are no limitations aside from the retention limits (so with default retention times you can only export 3 months of data).
Only limitation at the moment would be that the error details / network explorer information is not in this export. But this is collecting all the per-second high fidelity analytics data that powers the session log, playback graph etc…

  • Can we use any other cloud service provider apart from AWS/Azure/GCS? Since we currently have our entire infra on Oracle Cloud?

Unfortunately not at the moment - we only support AWS/Azure/GCS. Does Oracle have a S3 Compatible Storage option? That would be something we might be able to integrate :thinking:

  • Under the output key for the POST Exports API request body, there is confusion as to what value is expected in the outputId field. Is this any custom id that we can provide it with (as understood by the term <YOUR_OUTPUT_ID> used in the examples, or is it a value to be obtained from another API response and used here? (as understood by “A configuration that holds the ID of an existing Analytics Output”)

The outputId should be the ID of the output resource you created previously.
The idea here is to only specify the output bucket (eg. your S3 bucket with accessKey and secretKey as well as the bucket name) once and then be able to re-use the same destination for multiple exports in the future. Where you can set the path inside that bucket on the POST to the Export API without having to re-transmit credentials etc every time.
This might not be immediately obvious from the docs but there is an article on how to create such an output resource here: Bitmovin Docs - Analytics Tutorials | How to create an S3 Role-Based Output for Analytics exports

Hope this helps,
greetings Daniel

3 Likes