Why no custom log agent collector for app service?

[litan1106]

Why no custom log agent collector for app service? We were forced to use agentless method. https://docs.datadoghq.com/logs/log_collection/csharp/?tab=serilog#agentless-logging

It would be great to included the log agent into the App Service Extension as well. (where we can use environment variables to enable the log agent and customize the log path.)

example:

• DD_LOG_ENABLED: "true",
• DD_LOG_PATH: "D:\Home\LogFiles\myapp\web-.log" # Log path wildcard

[colin-higgins]

Hi @litan1106 thanks for the report.
No code change log collection is coming to the app service extension soon.
This is currently in progress. I'll update you here as soon as it is available.

[colin-higgins]

This will be in the next release: DataDog/dd-trace-dotnet#2240

[asalvo]

@colin-higgins Does this also mean that other logging providers such as NLog would now work with Azure App Services? If so is there an ETA on the release. We are currently in the middle of the 14 day trial and getting better support for NLog on Azure App Services would be a huge help for us.

https://docs.datadoghq.com/serverless/azure_app_services/?tab=net

This currently says that only serilog is supported.

"Sending logs from your application in Azure App Service to Datadog requires the use of Serilog. Submitting logs with this method allows for trace ID injection, which makes it possible to connect logs and traces in Datadog. To enable trace ID injection with the extension, add the application setting DD_LOGS_INJECTION:true."