Not Sure if i need to migrate to DCR based ingestion ?

Question

Not Sure if i need to migrate to DCR based ingestion ?

Patrick Wellink 20

Ok, I got a mail stating :

Data Collector API will be retired on 14 September 2026 – transition to DCR-based custom log ingestion.

You’re receiving this email because you currently use the Data Collector API for ingestion of custom logs to Azure Monitor logs.

But I am a little bit lost what is what. I send json data to log analytics directly through the REST API.

https://learn.microsoft.com/en-us/rest/api/loganalytics/create-request

The uri format is : https://{CustomerID}.ods.opinsights.azure.com/<Resource>?api-version=2016-04-01

It's a really simple REST api post and I really like that. I then query Log Analytics directly with kusto.

Do I understand correct that I have to migrate to DCR based log ingestion ?

I only need to insert the data into log analytics. They are not the default logs (events,metrics etc) but a specific json class. for each record I need to insert I call this API just to insert the data into log analytics.......

It's not really clear to me if i have to migrate ?

SwathiDhanwada-MSFT 19,093 Reputation points Moderator

2023-10-10T15:34:54.4866667+00:00

Patrick Wellink Hope the information is provided is useful. Do revert if you have further questions.
SwathiDhanwada-MSFT 19,093 Reputation points Moderator

2023-10-18T05:36:26.5633333+00:00

Patrick Wellink Have you had chance to review my previous comment? Kindly revert if you have further questions.

1 answer

Your answer

SwathiDhanwada-MSFT 19,093 Reputation points Moderator

2023-10-10T15:34:54.4866667+00:00

Patrick Wellink Hope the information is provided is useful. Do revert if you have further questions.
SwathiDhanwada-MSFT 19,093 Reputation points Moderator

2023-10-18T05:36:26.5633333+00:00

Patrick Wellink Have you had chance to review my previous comment? Kindly revert if you have further questions.

Answer 1

SwathiDhanwada-MSFT 19,093 Moderator

Patrick Wellink Welcome to Microsoft Q & A Community Forum. I understand that HTTP Data Collector API is easier for ingesting the data into table but however the Logs Ingestion API provides more processing power and greater flexibility in ingesting logs and managing tables than the legacy HTTP Data Collector API. Kindly note that the Log Ingestion API provides the following advantages over the Data Collector API:

Supports transformations, which enable you to modify the data before it's ingested into the destination table, including filtering and data manipulation.
Lets you send data to multiple destinations.
Enables you to manage the destination table schema, including column names, and whether to add new columns to the destination table when the source data schema changes.

To avoid ingestion errors and data loss, transition to the DCR-based Log Ingestion API before 14 September 2026. After this date, Data Collector API endpoints will become unavailable.

Patrick Wellink 20 Reputation points

2023-10-13T06:57:13.7633333+00:00

Yes but the HTTP Data Collector API is exactly what i wanted. Just push some data into log analytics..

Is this really going to be completely deprecated ?

The data I send is a custom record just in the format as i need it. I don't need the transformations and other stuff.....

I looked at DCR but there is not even the possibillity for custom JSON.....
SwathiDhanwada-MSFT 19,093 Reputation points Moderator

2023-10-17T09:06:10.38+00:00

Patrick Wellink I understand that HTTP Data Collector API is exactly what is needed for you. However, it has already been deprecated. Though it is now functional till 14 September 2026, there may be ingestion errors and data loss you may encounter if you continue using the HTTP Collector API.

I would highly recommend using Log Ingestion API to send your custom data. You can follow this document to migrate from HTTP Data Collector API to Log Ingestion API. If you need any assistance in migrating, do comment here. I will help you.