agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/observability/SKILL.md

observability

Skill46 starsChanged 8 months agoMITView on GitHub

Power Platform observability, telemetry, and monitoring. Use when: Application Insights, App Insights, monitoring, telemetry, observability, alerting, diagnostics, Monitor tool, tracing, plugin traces, form load times, flow telemetry, Automation Center, dashboards, KQL.

90 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gitops, background-jobs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kcns008Skill

    gitops

    GitOps Agent (Flow) — manages ArgoCD applications, Helm charts, Kustomize overlays, deployment strategies (canary, blue-green, rolling), multi-cluster GitOps, and drift detection for Kubernetes and OpenShift clusters.

    Also in 4 projects that use this

  • YepAPISkill

    background-jobs

    Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.

    Also in 4 projects that use this

  • Mushfiqur-Rahman-RobinSkill

    rag-systems

    Best practices for building Retrieval-Augmented Generation systems — chunking, embedding, hybrid retrieval, reranking, indexing, caching, evaluation, observability — plus a catalog of RAG patterns and when each applies.

    Also in 3 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 4 projects that use this

  • wpankSkill

    caching

    Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.

    Also in 5 projects that use this

  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 13 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No observability at all (flying blind in production)

    line 54
  2. Distinctive:

    Not enabling Managed Environments (platform telemetry export requires it)

    line 57
  3. Distinctive:

    No custom events in apps (platform telemetry is too generic for business insight)

    line 59
  4. Distinctive:

    No dashboard for stakeholders (telemetry exists but nobody looks at it)

    line 61

“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Observability & Monitoring

When to Use

Trigger when configuring Application Insights for Power Platform, setting up telemetry for model-driven apps, canvas apps, Code Apps, or flows, creating alert rules, building monitoring dashboards, or diagnosing performance issues using telemetry data.


Observability Stack

LayerToolData
Platform telemetryApplication Insights (via Managed Environments export)Dataverse API calls, plugin execution, SDK operations, exceptions
Model-driven appsApplication Insights + browser telemetryForm load times, JS errors, custom events
Canvas appsApplication Insights + Monitor toolScreen transitions, data call durations, delegation warnings
Code AppsApplication Insights SDK (@microsoft/applicationinsights-web)React errors, custom events, performance marks
Power AutomateAutomation Center + Application Insights (Managed Env)Flow run telemetry, action-level timing, failures
Copilot StudioAgent analytics + Application InsightsSession metrics, topic resolution, escalation rates

⚠️ REQUIRED: Load Sub-Files Before Implementation

SKILL.md is a summary only — it is NOT sufficient for implementation.

The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:

  • Application Insights Setup — connection string configuration, Managed Environments requirement, per-component enablement, environment-level export, instrumentation key vs connection string
  • Model-Driven App Telemetry — form load times, JavaScript errors, plugin traces (ITracingService + ILogger), custom events, performance markers
  • Canvas App Telemetry — screen transitions, data call durations, delegation warnings, Monitor tool real-time diagnostics, canvas app insights
  • Flow Telemetry — Power Automate flow run telemetry, Automation Center dashboard, run history analytics, action-level telemetry
  • Code App Telemetry — React error boundaries to App Insights, @microsoft/applicationinsights-web setup, custom events, performance marks, platform logger integration
  • Alerting & Dashboards — alert rules, action groups, KQL queries for common scenarios, Azure Dashboard templates

Telemetry Decision Table

QuestionAnswer
Where does platform telemetry go?Application Insights (requires Managed Environment + export config)
Where does custom app telemetry go?Same or separate Application Insights instance (your choice)
Should I use one App Insights per environment?Yes — one-to-one mapping for accurate reporting
Do I need Managed Environments?Yes for platform telemetry export, flow telemetry, and some advanced features
Can I use instrumentation key?No — use connection string (instrumentation key ingestion deprecated March 2025)

Anti-Patterns

  • No observability at all (flying blind in production)
  • Using instrumentation key instead of connection string (deprecated)
  • Sharing one Application Insights instance across multiple environments (mixed data, unusable reports)
  • Not enabling Managed Environments (platform telemetry export requires it)
  • Monitoring only after incidents (set up proactive alerts from day 1)
  • No custom events in apps (platform telemetry is too generic for business insight)
  • Alert fatigue (too many noisy alerts that get ignored)
  • No dashboard for stakeholders (telemetry exists but nobody looks at it)
  • Telemetry in dev but not in production (monitor where it matters)

Related Skills

  • env-strategy — Managed Environments enablement for telemetry export
  • governance — CoE Starter Kit for inventory and adoption monitoring
  • plugins — ITracingService and ILogger for plugin telemetry
  • code-apps — Code App telemetry setup with App Insights SDK
  • power-automate — Flow analytics and run history

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.