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
- virtualrussel/dynatrace-ai-dtctl-workspaceword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- virtualrussel/dynatrace-ai-dtctl-workspace★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- dt-alertingSkill
- dt-app-dashboardsSkill
- dt-app-notebooksSkill
- dt-dql-essentialsSkill
- dt-js-runtimeSkill
- dt-migrationSkill
- dt-obs-analyticsSkill
- dt-obs-awsSkill
- dt-obs-azureSkill
- dt-obs-compliance-assistantSkill
- dt-obs-ext-monitorsSkill
- dt-obs-frontendsSkill
- dt-obs-gcpSkill
- dt-obs-genaiSkill
- dt-obs-hostsSkill
- dt-obs-kubernetesSkill
- dt-obs-log-semantic-mappingSkill
- dt-obs-logsSkill
- dt-obs-network-devicesSkill
- dt-obs-network-flowsSkill
- dt-obs-predictive-analyticsSkill
- dt-obs-problemsSkill
- dt-obs-servicesSkill
- dt-obs-tracingSkill
- dt-platform-costsSkill
- dt-sec-contextualizationSkill
- dt-sec-insightsSkill
- dt-sec-ioc-huntingSkill
- dt-sec-semantic-mappingSkill
- dt-setup-androidSkill
- dt-setup-flutterSkill
- dt-setup-genaiSkill
- dt-setup-iosSkill
- dt-setup-oneagentSkill
- dt-setup-openinference-migrationSkill
- dt-setup-react-nativeSkill
- dt-upgradeSkill
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
- Very specific: line 44
If a status is not OK, get detailed logs:
- Very specific: line 51
Look for error codes in the content field.
- Distinctive: line 87
Run the status query above to identify the specific status code
- Distinctive: line 88
Check the status reference table for remediation
- Distinctive: line 89
If unclear, fetch event logs for the extension
- Very specific: line 93
Search for the code in references/extensions-error-codes.md (see Error Code Reference below)
- Very specific: line 94
If no error code is present, read the event content for details
- Very specific: line 97
Check for HIGH_CPU_RESTART, HIGH_MEMORY_RESTART, or TIMED_OUT_RESTART
- Very specific: line 102
Verify status is OK (not IDLE or error state)
- Distinctive: line 103
Check that the monitoring configuration is enabled
- Distinctive: line 104
Verify network connectivity to the monitored system
- Very specific: line 122
Do not load the full file: Search for the specific error code heading (e.g.
≈ “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.
Files
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 namedt.extension.config.id— monitoring configuration IDdt.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
| 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 |
IDLE | Working but no status produced | Usually transient |
WARNING | Warning state | Check extension logs |
GENERIC_ERROR | Error state | Check extension logs |
STARTUP_ERROR | Error during startup | Check extension logs and configuration |
HIGH_CPU / HIGH_CPU_RESTART | Excessive CPU usage | Switch Performance Profile in ActiveGate settings |
HIGH_MEMORY / HIGH_MEMORY_RESTART | Excessive memory usage | Switch Performance Profile in ActiveGate settings |
EEC_HARD_LIMIT_REJECTION / EEC_HARD_LIMIT_RESTART | Resource hard limit hit | Switch Performance Profile in ActiveGate settings |
EEC_RESTSERVER_ERROR | REST API port conflict | Check for port conflicts on the host |
EXTENSIONS_CACHE_ERROR | Cannot download extension | Check disk space on ActiveGate/OneAgent |
EXTENSION_VERIFICATION_ERROR | Malformed extension.yaml | Validate extension.yaml syntax |
CUSTOM_CODE_EXTENSION_NOT_ALLOWED | Custom code blocked | Update ActiveGate or OneAgent |
INCOMPATIBLE_API_ERROR | API version mismatch | Update ActiveGate/OneAgent or check extension docs |
MAX_TASKS_LIMIT_REJECTION | Too many tasks | Add ActiveGates to the group or split groups |
MISSING_BINARY / MISSING_DATASOURCE | Malformed installation | Reinstall ActiveGate or OneAgent |
GROUP_NAME_CHANGE | Temporary rebalancing | Wait for rebalancing to complete |
Troubleshooting
Common Issues
- 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
- 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
contentfor details
- Error codes follow the pattern
- Extension keeps restarting
- Check for
HIGH_CPU_RESTART,HIGH_MEMORY_RESTART, orTIMED_OUT_RESTART - Switch to a higher Performance Profile in ActiveGate settings
- Review extension configuration for excessive scope
- Check for
- Extension not producing data
- Verify status is
OK(notIDLEor error state) - Check that the monitoring configuration is enabled
- Verify network connectivity to the monitored system
- Verify status is
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
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
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.

