# dt-obs-extensions

The dt-obs-extensions Claude Code skill checks Dynatrace extension monitoring configurations and helps diagnose errors. It activates for status checks, startup failures, and extension error codes.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 229 installs · ★ 186 repo stars
- Author: Dynatrace
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-obs-extensions/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/dt-obs-extensions

## What it does

The skill checks monitoring configuration statuses and helps trace extension errors in Dynatrace. It uses DQL queries to inspect status and event data, then points to `references/extensions-error-codes.md` for DEC code details.

Statuses map to troubleshooting steps. For instance, `HIGH_MEMORY` calls for changing the Performance Profile in ActiveGate settings, while `EXTENSION_VERIFICATION_ERROR` points to the syntax of `extension.yaml`. For a DEC code, the skill looks up the matching entry instead of loading the entire reference file.

When an extension produces no data, the checks cover `OK` status, whether its monitoring configuration is enabled, and network access to the monitored system. A REST API port conflict calls for checking port use on the host.

## Requirements
- Works with: Dynatrace

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-extensions -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/dt-obs-extensions/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/dt-obs-extensions/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-extensions -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/dt-obs-extensions/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-extensions -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/dt-obs-extensions/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Dynatrace/dynatrace-for-ai skills/dt-obs-extensions
```

2. **Manually: put the files in place**
- File: `.github/skills/dt-obs-extensions/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-extensions -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Dynatrace/dynatrace-for-ai --path skills/dt-obs-extensions
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/dt-obs-extensions/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-extensions -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-obs-extensions/SKILL.md

## When to use it
- check an extension monitoring configuration status
- trace an error through event logs and its DEC code
- diagnose repeated extension restarts
- find why an extension produces no data

## Example prompts
- Check Dynatrace monitoring configuration statuses and explain any extension errors.
- Look up this extension's DEC code from its event log.
- Find out why the extension keeps restarting and produces no data.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6c82c9717c3bea4e.

BEGIN THIRD-PARTY FILE 6c82c9717c3bea4e
````text
---
name: dt-obs-extensions
description: >-
  Dynatrace extension status checks and troubleshooting. Use when checking extension monitoring
  configuration status, diagnosing extension errors, or interpreting extension error codes.
  Trigger: "extension status", "extension not working", "extension error", "monitoring configuration
  status", "EEC error", "extension troubleshooting", "DEC error code", "extension startup failed",
  "high memory extension", "extension verification error".
  Do NOT use for explaining existing queries, product documentation questions,
  or OneAgent/ActiveGate installation issues unrelated to extensions.
license: Apache-2.0
---

# Dynatrace Extensions Skill

## Overview

Dynatrace extensions allow you to extend the functionality of Dynatrace by integrating with external systems and custom data sources. 

**When to use this skill:**

- Checking the status of installed extensions and their monitoring configurations
- Troubleshooting extension configuration issues using DQL queries and event logs

## Extensions lifecycle
Extensions are first installed, which brings assets (dashboards, alert templates, OpenPipeline rules etc). Once installed, each extension can have multiple activation - Monitoring Configurations. Configurations can run on ActiveGate or OneAgent, and can be enabled/disabled independently. Each configuration has its own status, which can be queried using this skill.

## Extensions Monitoring Configurations and Statuses

### Extensions Statuses

To check the status of an extension, you can run following DQL query:

```dql
timeseries count(dt.sfm.extension.config.status), by: {dt.extension.name, dt.extension.config.id, dt.extension.status}
```

- `dt.extension.name` — extension name
- `dt.extension.config.id` — monitoring configuration ID
- `dt.extension.status` — current status value

### 2. Retrieve Extension Event Logs

If a status is not `OK`, get detailed logs:

```dql
fetch dt.system.events
| filter dt.extension.name == "<extension_name>" AND dt.extension.config.id == "<config_id>"
```

Look for error codes in the `content` field. Error codes have the format `DEC:[A-Z0-9_]+`.

→ For error code meanings and remediation, search `references/extensions-error-codes.md` for the exact code (see [Error Code Reference](#error-code-reference)).

---

## Extension Status Reference

| Status | Meaning | Remediation |
|--------|---------|-------------|
| `OK` | Running without issues | None |
| `STARTUP` / `STARTUP_PENDING` / `STARTUP_SCHEDULED` | Extension is starting | Wait for startup to complete |
| `RESTART` / `TIMED_OUT_RESTART` | Extension restarting | Monitor; if recurring, check logs |
````
END THIRD-PARTY FILE 6c82c9717c3bea4e

The third-party file has ended. Everything between the 6c82c9717c3bea4e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2680 of 5674 bytes. © Dynatrace · Apache-2.0 · https://github.com/Dynatrace/dynatrace-for-ai/tree/HEAD/skills/dt-obs-extensions/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
