agentleFS
DynatraceDynatrace/dynatrace-for-ai/skills/dt-obs-extensions/SKILL.md

dt-obs-extensions

Skill176 starsChanged 14 days agoApache-2.0View on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a status is not OK, get detailed logs:

    line 44
  2. Very specific:

    Look for error codes in the content field.

    line 51
  3. Distinctive:

    Run the status query above to identify the specific status code

    line 87
  4. Distinctive:

    Check the status reference table for remediation

    line 88
  5. Distinctive:

    If unclear, fetch event logs for the extension

    line 89
  6. Very specific:

    Search for the code in references/extensions-error-codes.md (see Error Code Reference below)

    line 93
  7. Very specific:

    If no error code is present, read the event content for details

    line 94
  8. Very specific:

    Check for HIGH_CPU_RESTART, HIGH_MEMORY_RESTART, or TIMED_OUT_RESTART

    line 97
  9. Very specific:

    Verify status is OK (not IDLE or error state)

    line 102
  10. Distinctive:

    Check that the monitoring configuration is enabled

    line 103
  11. Distinctive:

    Verify network connectivity to the monitored system

    line 104
  12. Very specific:

    Do not load the full file: Search for the specific error code heading (e.g.

    line 122

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

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:

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:

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).


Extension Status Reference

StatusMeaningRemediation
OKRunning without issuesNone
STARTUP / STARTUP_PENDING / STARTUP_SCHEDULEDExtension is startingWait for startup to complete
RESTART / TIMED_OUT_RESTARTExtension restartingMonitor; if recurring, check logs
IDLEWorking but no status producedUsually transient
WARNINGWarning stateCheck extension logs
GENERIC_ERRORError stateCheck extension logs
STARTUP_ERRORError during startupCheck extension logs and configuration
HIGH_CPU / HIGH_CPU_RESTARTExcessive CPU usageSwitch Performance Profile in ActiveGate settings
HIGH_MEMORY / HIGH_MEMORY_RESTARTExcessive memory usageSwitch Performance Profile in ActiveGate settings
EEC_HARD_LIMIT_REJECTION / EEC_HARD_LIMIT_RESTARTResource hard limit hitSwitch Performance Profile in ActiveGate settings
EEC_RESTSERVER_ERRORREST API port conflictCheck for port conflicts on the host
EXTENSIONS_CACHE_ERRORCannot download extensionCheck disk space on ActiveGate/OneAgent
EXTENSION_VERIFICATION_ERRORMalformed extension.yamlValidate extension.yaml syntax
CUSTOM_CODE_EXTENSION_NOT_ALLOWEDCustom code blockedUpdate ActiveGate or OneAgent
INCOMPATIBLE_API_ERRORAPI version mismatchUpdate ActiveGate/OneAgent or check extension docs
MAX_TASKS_LIMIT_REJECTIONToo many tasksAdd ActiveGates to the group or split groups
MISSING_BINARY / MISSING_DATASOURCEMalformed installationReinstall ActiveGate or OneAgent
GROUP_NAME_CHANGETemporary rebalancingWait for rebalancing to complete

Troubleshooting

Common Issues

  1. Extension shows non-OK status
    • Run the status query above to identify the specific status code
    • Check the status reference table for remediation
    • If unclear, fetch event logs for the extension
  2. Error codes in event logs
    • Error codes follow the pattern DEC:[A-Z0-9_]+
    • Search for the code in references/extensions-error-codes.md (see Error Code Reference below)
    • If no error code is present, read the event content for details
  3. Extension keeps restarting
    • Check for HIGH_CPU_RESTART, HIGH_MEMORY_RESTART, or TIMED_OUT_RESTART
    • Switch to a higher Performance Profile in ActiveGate settings
    • Review extension configuration for excessive scope
  4. Extension not producing data
    • Verify status is OK (not IDLE or error state)
    • Check that the monitoring configuration is enabled
    • Verify network connectivity to the monitored system

Error Code Reference

references/extensions-error-codes.md is a large generated file. Each entry follows this structure:

## Error Code DEC:<code>

### Error Description: <description>

### Suggestions:

1. ...

Do not load the full file. Search for the specific error code heading (e.g. ## Error Code DEC:1D6) in references/extensions-error-codes.md and read the next ~50 lines. Stop at the next ## Error Code header.


References

  • extensions-error-codes.md — Complete list of DEC error codes with descriptions and troubleshooting steps

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.