azure-monitor-ingestion-java

Topics in the source

• Azure Monitor Ingestion SDK for Java
• Installation
• Prerequisites
• Environment Variables
• Client Creation
• Synchronous Client
• Asynchronous Client
• Key Concepts

Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules. Or use Azure SDK BOM: Data Collection Endpoint (DCE) Data Collection Rule (DCR) Log Analytics workspace Target table (custom or built-in: CommonSecurityLog, SecurityEvents, Syslog, WindowsEvents) | Concept | Description | |---------|-------------| | Data Collection Endpoint (DCE) | Ingestion endpoint URL for your region | | Data Collection Rule (DCR) | Defines data transformation and routing to tables | | Stream Name | Target stream in the DCR (e.g., Custom-MyTableCL) | | Log Analytics Workspace | Destination for ingested logs | For large log collections, enable concurrent uploads: Handle partial upload failures gracefully: 1. Batch logs — Upload in batches rather than one at a time 2. Use concurrency — Set maxConcurrency for large uploads 3. Handle partial failures — Use error consumer to log failed entries 4. Match DCR schema — Log entry fields must match DCR transformation expectations 5. Include TimeGenerated — Most tables require a timestamp field 6. Reuse client — Create once, reuse throughout application 7. Use async for high throughput — LogsIngestionAsyncClient f

This is an excerpt. Refer to the complete source and its current requirements.