Observability logo

Observability

Community
korchard333
observability

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.

Overview

Publisherkorchard333
Repositoryclaude-power-platform-community
Skill nameobservability
Stars
50
Forks
6
Bundled files
7
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by korchard333 on GitHub. Read the source before you install it.

Installation

Install the Observability AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/observability
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/korchard333/claude-power-platform-community.git /tmp/claude-power-platform-community
mkdir -p .claude/skills
cp -r /tmp/claude-power-platform-community/.claude/skills/observability .claude/skills/observability
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Observability in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Observability on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Observability is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Observability AI skill do?

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.

Why use Observability on TypingMind?

Because you install it once and use it with any model. Observability is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Observability in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/observability. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Observability?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Observability?

As many as you like. As long as a model supports skills, you can use Observability with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Observability AI skill free?

Yes. It is published on GitHub by korchard333 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇