Hi, If someone is using openTelemetry inside Azure Container App , I wanted to understand what kind of patterns are you using. I don't want to use Docker Compose as suggested in this link as it violates Single Responsibility Principal. Also another issue in running the Otel Collector in same machine is that loss of logs if the collector and the application are running in same containers and the application gets terminated and replica restart leading to loss of logs..... So I wanted to check how anyone who is using azure container apps are using opentelemetry. What are you using. Something that I had in mind was :- 1. Using Sidecar containers. 2. DAPR which is natively proviced by Azure Container App. 3. Gateway Pattern - collector is hosted somewhere and we push logs directly via SDK to the receiver. feel free to suggest any good and robust way that has worked for you. FYI: Our tech stack is NodeJS running inside the docker. cc - @Ritesh Kumar

Hey Avneesh, Azure container apps does not support anything like a Daemonset (though it uses k8s under the hood). to avoid violation of Single Responsibility Principal

@Shivanshu Raj Shrivastava Got it... Am proceeding with third.. Will let you know if I face any issue.

Sure!!

Hey @Avneesh Kumar We are in the process of writing Azure Docs and 3 is recommended. Which in the docs is dubbed as the “Central Collector” In addition to being a central deployment it scrapes metrics from Azure Monitor and Consumes event bus for Infra metrics and Infra logs. Here is a Draft version of it for reference*:* https://deploy-preview-1657--frosty-austin-928e43.netlify.app/docs/azure-monitoring/bootstrapping/