用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Arvo-AI/aurora --skill dynatrace命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | dynatrace |
| id | dynatrace |
| description | Dynatrace APM integration for querying problems, logs, metrics, and monitored entities during RCA investigations |
| category | observability |
| connection_check | {"method":"is_connected_function","module":"chat.backend.agent.tools.dynatrace_tool","function":"is_dynatrace_connected"} |
| tools | ["query_dynatrace"] |
| index | APM platform -- query problems, logs, metrics, entities via Dynatrace API |
| rca_priority | 3 |
| allowed-tools | query_dynatrace |
| metadata | {"author":"aurora","version":"1.0"} |
Dynatrace integration for querying APM data during Root Cause Analysis. Dynatrace is a REMOTE service. Use ONLY the query_dynatrace API tool. All data is accessed via a single unified tool with resource_type parameter.
query_dynatrace(resource_type=TYPE, query=SELECTOR, time_from=START, time_to=END, limit=N)
'problems' -- Active/recent problems. query=problem selector e.g. status("open")'entities' -- Monitored hosts/services/processes. query=entity selector e.g. type("HOST")'logs' -- Log entries. query=search string'metrics' -- Metric time series. query=metric selector e.g. builtin:host.cpu.usagestatus("open"), status("closed"), severityLevel("ERROR")type("HOST"), type("SERVICE"), type("APPLICATION"), type("PROCESS_GROUP")builtin:host.cpu.usage, builtin:host.mem.usage, builtin:service.response.timenow-1h, now-2h, now-24hnow-2hquery_dynatrace(resource_type='problems', query='status("open")', time_from='now-1h')query_dynatrace(resource_type='metrics', query='builtin:host.cpu.usage', time_from='now-30m')query_dynatrace(resource_type='entities', query='type("HOST")', time_from='now-1h')query_dynatrace(resource_type='logs', query='error', time_from='now-1h')Step 1 -- Check active problems:
Start with problems to understand the current issue landscape.
query_dynatrace(resource_type='problems', query='status("open")', time_from='now-2h')
Step 2 -- Drill into affected entities:
Identify which hosts, services, or processes are impacted.
query_dynatrace(resource_type='entities', query='type("HOST")', time_from='now-2h')
Step 3 -- Search logs for errors:
Find error messages around the alert time.
query_dynatrace(resource_type='logs', query='ERROR', time_from='now-1h')
Step 4 -- Query metrics for resource patterns:
Check CPU, memory, and response time metrics for anomalies.
query_dynatrace(resource_type='metrics', query='builtin:host.cpu.usage', time_from='now-1h')
query_dynatrace API tool.resource_type parameter is required and must be one of: problems, logs, metrics, entities.problems to understand the issue, then drill into entities and logs.logs.read is required for log queries, metrics.read for metric queries. A 403 error indicates a missing scope.