Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE). Triggers: "LogsIngestionClient java", "azure monitor ingestion java", "custom logs java", "DCR java", "data collection rule java".
SkillScore100Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/10/2026
What it changes
Passed 22 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill100%
Checks it passed that the model alone missed
The environment variable for stream identification is STREAM_NAME
The environment variable for endpoint location is DATA_COLLECTION_ENDPOINT
The environment variable name AZURE_TOKEN_CREDENTIALS is explicitly referenced
and 11 more in the full report
7 fixed15 passed either way0 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+42%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/10/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
What standard environment variable names should be configured in our container environment for Azure Monitor log upload routing, stream identification, and data collection endpoints?
What was checked, without and with the skill
Checked
Without skill
With skill
The environment variable for endpoint location is DATA_COLLECTION_ENDPOINT
Missed
Passed
The environment variable for routing rule identification is DATA_COLLECTION_RULE_ID
Missed
Passed
The environment variable for stream identification is STREAM_NAME
Missed
Passed
case-13 · gemini-3.6-flash · 8/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md231 lines2 files
Azure Monitor Ingestion SDK for Java
Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.