Coralogix Status - Direct Archive Query HTTP API - Adding new Json object to response

Direct Archive Query HTTP API - Adding new Json object to response

Scheduled Maintenance Report for Coralogix

Completed

The scheduled maintenance has been completed.

Posted Sep 16, 2024 - 10:00 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted Sep 16, 2024 - 09:01 UTC

Scheduled

As part of our commitment to delivering better service, we are planning to deploy additional Json objects to the ndjson responses from the Direct Archive Query HTTP API - https://coralogix.com/docs/direct-query-http-api/.

What Does This Mean for You?
If you are running any automations based on these responses, please ensure that your automation scripts can handle additional Json objects beyond just the result object.

Examples of Additional Objects:
{ "warning": {...} }
{ "query.metadata": {...} }

We recommend updating your scripts and automations to accommodate these changes and additional similar changes in the future to ensure continued seamless operation.

To test if your script works as expected following the change, you can add "withQueryId=true" to the end of the api endpoint you use.

September 12th update:
Please note that the changes will only add new JSON objects without removing any existing ones. Therefore, your script adjustments should be agnostic to additional objects and should reference the response object. We suggest having a default that will return the entire payload in case of illegal queries.

If you have any questions or need assistance, please feel free to contact our support team.

Posted Aug 07, 2024 - 07:01 UTC

This scheduled maintenance affected: EU1 (API - Fetch Data), EU2 (API - Fetch Data), US1 (API - Fetch Data), US2 (API - Fetch Data), AP1 (API - Fetch Data), and AP2 (API - Fetch Data).