-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Support for Log Ingestion API #80
Comments
@cbykarl thanks for bringing it up. Microsoft is notorious for deprecating/rebranding things for nothing ;) but I'll keep an eye on it. |
Looks like this is affected already. The library is unable to create a log table in the Log analytics workspace and nothing happening. Is there a workaround or a new version coming up? |
Looks like we have a date (https://azure.microsoft.com/en-us/updates/azure-monitor-data-collection-api-retirement/): "On 14 September 2026, we’ll retire Data Collector API for ingesting custom logs to Azure Monitor logs." |
I am planning to support new API as soon as time permits. But if any brave soul wants to contribute, its highly appreciated 👍🏼 |
I was just thinking about this, and I may need to jump in. It's been like 2 years since I've worked with this library and LA in Azure, and I'm still pretty dumbfounded still at how difficult Microsoft has made it to write to a custom LA log -- especially since I read in multiple places that this is the preferred way for isolating and querying application-specific logs. So I'm glad I found this thread, because I still don't think there's another library out there that makes it as intuitive as this one to accomplish the goal. As far as I can tell, the only current alternative, aside from writing your own like we're discussing, is using the ingestion API client SDK directly. This kinda takes the point away from using logging abstractions ... why haven't they addressed this in a similar fashion like for logging to app insights? |
Well the new way to go is to write to Azure Monitor. You will need a Data Collection Endpoint and a data collection rule. Once that is in place you can still write to log analytics only with a different Rule. |
Hello!
Is there any plans on adding support for sending log data using the Logs Ingestion API? From my understanding the "Data Collector API" that this package is using to send log data is treated as legacy by MSFT. Here is a migration guide they published in june.
Great package, thx so far! :)
The text was updated successfully, but these errors were encountered: