スキル Azure Monitor Ingestion SDK for Java
📦

Azure Monitor Ingestion SDK for Java

安全

Send Custom Logs to Azure Monitor with Java

Custom application logs need centralized monitoring in Azure. This skill helps you ingest logs to Azure Monitor using Data Collection Rules and the official Java SDK.

対応: Claude Codex Code(CC)
📊 69 十分
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「Azure Monitor Ingestion SDK for Java」を使用しています。 Create a LogsIngestionClient using DefaultAzureCredential with endpoint from environment variable

期待される結果:

DefaultAzureCredential credential = new DefaultAzureCredentialBuilder().build();

LogsIngestionClient client = new LogsIngestionClientBuilder()
.endpoint(System.getenv("DATA_COLLECTION_ENDPOINT"))
.credential(credential)
.buildClient();

「Azure Monitor Ingestion SDK for Java」を使用しています。 Upload 3 log entries to Azure Monitor with DCR ID and stream name

期待される結果:

List<Object> logs = new ArrayList<>();
logs.add(new MyLogEntry("2024-01-15T10:30:00Z", "INFO", "Application started"));
logs.add(new MyLogEntry("2024-01-15T10:30:05Z", "DEBUG", "Processing request"));
logs.add(new MyLogEntry("2024-01-15T10:30:10Z", "WARN", "High memory usage detected"));

client.upload(ruleId, streamName, logs);
System.out.println("Logs uploaded successfully");

セキュリティ監査

安全
v1 • 2/25/2026

Documentation-only skill containing usage examples for the official Azure Monitor Ingestion SDK for Java. No executable code, no security risks detected. Static analysis found 0 files with 0 suspicious patterns. The skill provides legitimate Azure SDK integration patterns with proper authentication using DefaultAzureCredential.

0
スキャンされたファイル
0
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
31
コミュニティ
100
セキュリティ
74
仕様準拠

作れるもの

Application Telemetry Ingestion

Send custom application logs, metrics, and events from Java applications to Azure Monitor for centralized monitoring and alerting.

Security Event Collection

Ingest security audit logs and compliance events to Azure Monitor SecurityEvents or CommonSecurityLog tables for SIEM integration.

Custom Business Metrics

Track business-specific events and KPIs by uploading structured logs to custom tables in Log Analytics workspace.

これらのプロンプトを試す

Basic Client Setup 
Create a synchronous LogsIngestionClient for Azure Monitor using environment variables for endpoint, DCR ID, and stream name. Include DefaultAzureCredential authentication.
Upload Logs with Error Handling 
Generate Java code to upload a list of custom log entries to Azure Monitor with partial failure handling. Log failed entries without aborting the entire batch.
Concurrent Large Upload 
Create an async upload method that sends 10000 log entries to Azure Monitor with maxConcurrency set to 5. Use Reactor Mono for reactive streaming.
Custom Log Entry Model 
Define a Java class for a custom log entry with timeGenerated, severity, source, and message fields. Include getters for JSON serialization required by the Logs Ingestion API.

ベストプラクティス

  • Batch log entries before uploading instead of sending one at a time for better performance
  • Set maxConcurrency option when uploading large log collections to improve throughput
  • Include TimeGenerated field in log entries as most Azure Monitor tables require timestamps

回避

  • Creating new client instances for each upload - reuse a single client throughout application lifecycle
  • Uploading logs synchronously in high-throughput scenarios - use async client for reactive patterns
  • Ignoring partial upload errors - always configure error consumer to handle failed entries

よくある質問

What prerequisites are needed before using this skill?
You need a Data Collection Endpoint (DCE), Data Collection Rule (DCR), Log Analytics workspace, and a target table configured in Azure Monitor.
How do I authenticate with Azure Monitor?
Use DefaultAzureCredential which supports managed identity, environment credentials, and other Azure authentication methods automatically.
Can I upload logs to custom tables?
Yes, you can upload to custom tables using the Custom- prefix in the stream name, or to built-in tables like CommonSecurityLog and SecurityEvents.
How do I handle upload failures?
Use LogsUploadOptions with setLogsUploadErrorConsumer to handle partial failures gracefully without aborting the entire batch.
What is the difference between sync and async clients?
Synchronous client blocks until upload completes. Async client returns Mono<Void> for non-blocking reactive patterns with better throughput.
How do I query the logs after ingestion?
Use the azure-monitor-query skill with LogsQueryClient to run KQL queries against your Log Analytics workspace.

開発者の詳細

作成者

sickn33

ライセンス

MIT

リポジトリ

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-monitor-ingestion-java

参照

main

ファイル構成

📄 SKILL.md