Skills azure-monitor-ingestion-py

📦

azure-monitor-ingestion-py

Name: azure-monitor-ingestion-py
Author: sickn33

Content revision r2 Safe ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

Send Custom Logs to Azure Monitor with Python

Sending structured logs to Azure Monitor requires correct endpoints, credentials, rules, and schemas. This skill provides Python patterns for synchronous, asynchronous, and resilient ingestion.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "azure-monitor-ingestion-py" from https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-monitor-ingestion-py/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-azure-monitor-ingestion-py.md Signed manifest GET /api/skills/sickn33-azure-monitor-ingestion-py/manifest Signed lockfile GET /api/skills/sickn33-azure-monitor-ingestion-py/lockfile

Test it

Using "azure-monitor-ingestion-py". Send application startup events to my custom Azure Monitor table.

Expected outcome:

A synchronous ingestion plan using environment configuration, DefaultAzureCredential, schema-aligned records, and an explicit upload call.

Using "azure-monitor-ingestion-py". Make my log uploader tolerate partial failures.

Expected outcome:

A retry strategy that captures failed records, reports diagnostics, limits repeated attempts, and preserves successful uploads.

Using "azure-monitor-ingestion-py". Configure this workflow for Azure Government.

Expected outcome:

A sovereign-cloud setup using the Azure Government authority, ingestion endpoint, and Monitor credential scope.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 33 static findings are false positives caused by Markdown formatting, standard Azure endpoint examples, or explicit configuration reads. No prompt injection, malicious command execution, credential exfiltration, or reconnaissance intent was found.

Files scanned

213

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (23)

🌐 Network access (3)

SKILL.md:24 SKILL.md:158 SKILL.md:160

📁 Filesystem access (1)

SKILL.md:160

🔑 Env variables (4)

SKILL.md:50 SKILL.md:63 SKILL.md:67 SKILL.md:68

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-monitor-ingestion-py/security.svg)](https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-monitor-ingestion-py/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-monitor-ingestion-py.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). azure-monitor-ingestion-py security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-monitor-ingestion-py-2026,
  author = {sickn33},
  title = {azure-monitor-ingestion-py security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-monitor-ingestion-py security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-monitor-ingestion-py/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-azure-monitor-ingestion-py:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Centralize Service Logs

Send structured application events from Python services into a shared Log Analytics workspace.

Add Custom Telemetry

Implement reliable Azure Monitor uploads with retries and partial-failure handling.

Support Sovereign Cloud

Configure ingestion endpoints, authority hosts, and scopes for Azure Government deployments.

Try These Prompts

Create a Basic Uploader

Create a minimal Python example that sends sample logs to Azure Monitor using environment variables and DefaultAzureCredential.

Ingest Existing Events

Adapt my Python event records for a custom Log Analytics table and identify required Data Collection Rule fields.

Handle Partial Failures

Design upload error handling that records failed entries, limits retries, preserves diagnostics, and avoids duplicate ingestion.

Scale Government Ingestion

Plan asynchronous Azure Government ingestion with credential scope, client cleanup, bounded concurrency, retries, and schema validation.

Best Practices

Match every log field and type to the Data Collection Rule schema.
Use managed identity or another DefaultAzureCredential source instead of embedded secrets.
Record partial failures and apply bounded retries with duplicate protection.

Avoid

Do not hardcode client secrets, tenant secrets, or production credentials.
Do not silently ignore upload failures in production workflows.
Do not upload local files before reviewing their contents and destination.

Frequently Asked Questions

What Azure resources are required?

You need a Log Analytics workspace, Data Collection Endpoint, Data Collection Rule, and destination table.

Does this skill create Azure resources?

No. It provides Python ingestion patterns for resources that already exist.

How does authentication work?

Examples use DefaultAzureCredential, which can select configured local, managed identity, or workload identity credentials.

Can it upload records from a file?

Yes. The documented workflow loads records from a JSON file, then passes them to the ingestion client.

Does it support asynchronous uploads?

Yes. It includes the asynchronous LogsIngestionClient and context-managed cleanup.

Does it support Azure Government?

Yes. It shows the Azure Government authority host, ingestion endpoint format, and credential scope.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

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

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

6 downloads · 162 views

File structure

📄 SKILL.md