azure-monitor-ingestion-java

You can send custom logs to Azure Monitor from Java by using the Logs Ingestion API via Data Collection Rules (DCR) and Data Collection Endpoints (DCE) to reliably upload structured log entries. The SDK handles batching, authentication, and endpoint configuration.

Synchronous log ingestion blocks the Java application until the upload completes, while asynchronous ingestion allows reactive streaming workflows. Both use the Logs Ingestion API to send custom logs to Azure Monitor via configured DCR and DCE endpoints.

Yes, Data Collection Rules (DCR) and Data Collection Endpoints (DCE) are prerequisites for publishing logs. They define the target schema and ingestion endpoint, allowing the Java client to route custom log data correctly to Azure Monitor.

Yes, the Java Azure Monitor Ingestion client supports credential handling with DefaultAzureCredential. This allows you to authenticate log ingestion requests to your DCE securely without managing explicit secrets in your application code.

The best way to upload structured POJO-based logs is using the Azure Monitor Ingestion SDK for Java. It provides client libraries that format and batch your objects automatically, sending them to Azure Monitor through configured Data Collection Rules.

Batched log upload groups multiple custom log entries into a single request sent to the Azure Monitor Logs Ingestion API. The Java SDK manages this batching internally to reduce overhead and improve throughput for DCR-based log publishing.