[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWBJVPZ4WTY11JBJKSMQQD":3,"skill-same:01M7BWBJVPZ4WTY11JBJKSMQQD":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BWBJVPZ4WTY11JBJKSMQQD","dt-setup-oneagent",null,"Reference knowledge for installing, uninstalling, or creating-and-installing Dynatrace OneAgent across VM\u002Fserver, Kubernetes (Operator + DynaKube), AWS Lambda (layer + env vars, plus optional fresh function provisioning), Windows hosts, remote Linux hosts \u002F EC2 instances over SSH, and Azure VMs \u002F VM Scale Sets. Returns documented endpoints, env vars, token scopes, and copy-paste-ready commands. Returns the exact commands to run rather than executing them. Use when the user asks to install or uninstall OneAgent, or asks \"how do I…\", \"what URL\u002Fscope\u002Fvar do I need for…\", or \"explain the OneAgent deployment for X\".","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dt-setup-oneagent\ndescription: Reference knowledge for installing, uninstalling, or creating-and-installing Dynatrace OneAgent across VM\u002Fserver, Kubernetes (Operator + DynaKube), AWS Lambda (layer + env vars, plus optional fresh function provisioning), Windows hosts, remote Linux hosts \u002F EC2 instances over SSH, and Azure VMs \u002F VM Scale Sets. Returns documented endpoints, env vars, token scopes, and copy-paste-ready commands. Returns the exact commands to run rather than executing them. Use when the user asks to install or uninstall OneAgent, or asks \"how do I…\", \"what URL\u002Fscope\u002Fvar do I need for…\", or \"explain the OneAgent deployment for X\".\nlicense: Apache-2.0\n---\n\n# Deploy Dynatrace OneAgent — knowledge reference\n\nThis skill is **reference-only**. It contains the documented endpoints, environment variables, token scopes, and commands that an operator (or another agent) needs to install OneAgent manually across the supported targets. It executes nothing.\n\n> This skill gives you the commands; it does not run them. Follow the procedure for the target you need, substituting the environment URL and token as documented below.\n\n## Hard rules for any agent consuming this skill\n\n- **Operate only on resources the user explicitly named.** Never create a placeholder\u002Ftest Lambda, IAM role, K8s namespace, secret, S3 bucket, EC2 instance, or any other fixture on your own initiative — not to \"demonstrate\", not \"while we're at it\", not preemptively. If the named resource doesn't exist and the user hasn't asked for it to be created, stop and ask. Side resources (additional Secrets Manager entries, monitoring, helper stacks) must not be provisioned silently — surface them as confirmation questions with the exact definition first.\n- **Explicit user-driven create modes are fine.** When the user passes `--create` (or explicitly says \"yes, create it\" after being asked), provisioning exactly the resources documented for that mode is the right thing to do — see *Create a new function and install OneAgent* in [references\u002Faws-lambda.md](references\u002Faws-lambda.md) for the documented set. Don't second-guess the function name the user typed: do **not** pattern-match on names like \"test\", \"demo\", \"scratch\", \"tmp\" and refuse, warn, or insist on an alternative. The input is authoritative; the rule above is about *silent* or *unsolicited* creation, not user-requested creation.\n- **Never persist the API token.** The token's only job is to (a) authenticate the OneAgent artifact download \u002F layer-ARN lookup and (b) get handed to the target system (Lambda env var or Secrets Manager, Linux installer, DynaKube secret) as part of the install. Do not cache it to local files, write it to scratch scripts, leave it in shell history, copy it into PR descriptions, or store it anywhere outside the target system that strictly needs it. Treat each run as fresh: supply via env var or 0600 file, use, discard.\n- **Never echo or log the API token.** When you have to reference it in a command, write `$DT_API_TOKEN` or an elided prefix (`dt0s16.…`, `dt0c01.…`). Don't paste the literal value into prose.\n- **Never assume the env URL, and confirm the tenant before installing.** Targeting the wrong environment fails *silently*: the install succeeds and the host or function simply reports to a tenant nobody is watching. An environment URL the user stated explicitly always wins over anything derived from a tool default or a previous run — never let a cached or discovered value override it. State the tenant you are about to use and let the user correct you. Tenant IDs (`abc12345`) and labs vs. prod determine the correct host.\n- **Writes that take a collection replace it — read, merge, then write.** Several APIs here accept a whole collection and overwrite whatever was there: `aws lambda update-function-configuration` does this for **both** `--environment` and `--layers`, so sending only the Dynatrace values silently deletes the function's own variables and any other layers. Always read current state, merge your additions into it, and write the union back. Take a rollback snapshot before the first write. This applies wherever you are about to replace a set rather than add to one.\n- **Deriving the env URL from dtctl.** `dtctl config current-context` returns only the *context name* (e.g. `my-env`), not a URL. The URL comes from `dtctl config describe-context \u003Cctx>`. Do **not** pipe that straight into `jq`: some dtctl versions ignore `-o json` and print a human table (`Environment:  https:\u002F\u002F…`) while still exiting 0, so jq dies on a parse error and takes any `set -e -o pipefail` script down with it. Check the output really is JSON first, and fall back to scraping the `Environment:` line:\n\n```bash\nCTX=\"$(dtctl config current-context 2>\u002Fdev\u002Fnull || true)\"\nOUT=\"$(dtctl config describe-context \"$CTX\" -o json 2>\u002Fdev\u002Fnull || true)\"\nif printf '%s' \"$OUT\" | jq -e . >\u002Fdev\u002Fnull 2>&1; then\n  DT_ENV_URL=\"$(printf '%s' \"$OUT\" | jq -r '.environment \u002F\u002F .url \u002F\u002F empty')\"\nelse\n  DT_ENV_URL=\"$(printf '%s' \"$OUT\" | awk 'tolower($1) ~ \u002F^(environment|url):$\u002F {print $2; exit}')\"\nfi\n```\n\n---\n\n## URL normalization\n\nDynatrace's \"new platform\" URLs and the classic OneAgent installer endpoints differ. Before constructing installer URLs, convert:\n\n| Input (Dynatrace UI \u002F docs)            | Use for installer endpoints           |\n|----------------------------------------|---------------------------------------|\n| `https:\u002F\u002F\u003Cid>.apps.dynatrace.com`      | `https:\u002F\u002F\u003Cid>.live.dynatrace.com`     |\n| `https:\u002F\u002F\u003Cid>.\u003Cregion>.apps.dynatracelabs.com` | `https:\u002F\u002F\u003Cid>.\u003Cregion>.dynatracelabs.com` |\n| Anything else                          | unchanged                             |\n\nThe tenant ID is the first dot-separated segment (`\u003Cid>`).\n\n---\n\n## Token types and the Authorization header\n\nTwo token families are in play, and **the `Authorization` scheme is chosen by the token's prefix, not by which endpoint you call**:\n\n| Token | Prefix | Header |\n|---|---|---|\n| Platform token | `dt0s16.` | `Authorization: Bearer \u003Ctoken>` |\n| Access token (classic API token) | `dt0c01.` | `Authorization: Api-Token \u003Ctoken>` |\n| PaaS token | `dt0s01.` | `Authorization: Bearer \u003Ctoken>` |\n| OAuth client secret | `dt0s02.` \u002F `dt0s03.` | ❌ not directly usable — must be exchanged for a bearer token first |\n\n**Platform tokens are the forward-looking default.** Dynatrace is deprecating access tokens: new tenants can no longer create them, and Classic API endpoints are being updated to accept platform tokens. Do **not** assume a token starts with `dt0c01.`. The reference implementation of this rule is dtwiz's `AuthHeader()` (`pkg\u002Finstaller\u002Finstaller.go`): `dt0c01.*` → `Api-Token`, everything else → `Bearer`.\n\nOne path hands the token to a component that has historically required a PaaS\u002Faccess token — if it rejects a platform token, use a `dt0c01.` access token there:\n\n- **Kubernetes** — the Dynatrace Operator authenticates using the `dynakube` secret.\n\nVM, remote VM\u002FEC2, Windows and Lambda call the Deployment API directly and work with either family.\n\n## Token scopes by target\n\nFor a **platform token** (`dt0s16.`), the OneAgent-relevant scopes live under **Fleet management**: `fleet-management:oneagents:download`, `fleet-management:oneagent.connection-info:read`, `fleet-management:oneagent.tokens:read`, `fleet-management:cluster-id:read`; Kubernetes additionally wants `fleet-management:activegates:download` and `fleet-management:activegate.tokens:create`. Generating the token via the Dynatrace **QuickStart** app provisions a working set.\n\nFor a **classic access token** (`dt0c01.`):\n\n| Target          | Required token scopes |\n|-----------------|------------------------|\n| VM \u002F Windows    | `InstallerDownload` (PaaS) |\n| Kubernetes      | `InstallerDownload`, `settings.read`, `settings.write`, `activeGateTokenManagement.create` — the Dynatrace UI's \"Kubernetes: Dynatrace Operator\" template sets all four. |\n| Azure VM \u002F VMSS | `InstallerDownload` (PaaS). Azure side: the caller's `az` identity needs `Contributor` or any role granting `Microsoft.Compute\u002F...\u002Fextensions\u002Fwrite` on the resource. |\n| AWS Lambda (runtime token) | A **connection auth token** consumed by the OneAgent layer at runtime. Distinct from the installer token. Create from the Dynatrace UI under *Access tokens* with `entities.read`, or use the Hub → AWS Lambda template. |\n\nTokens are never username-scoped — they belong to the tenant.\n\n---\n\n## Targets\n\nEach target has its own reference. They share the rules, URL normalization and token guidance above — read those first, then the one you need.\n\nManaged Kubernetes distributions are covered inside the Kubernetes reference rather than separately: the install is identical and only the node type differs, so the deltas belong next to the procedure they modify.\n\n| Target | Reference |\n|---|---|\n| VM \u002F server (Linux, macOS) | below — the base case every other target builds on |\n| Remote VM \u002F EC2 over SSH | → [references\u002Fremote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| Windows host (WSL or native) | → [references\u002Fwindows.md](references\u002Fwindows.md) |\n| Kubernetes (Operator + DynaKube) — incl. **EKS**, Fargate and Bottlerocket limits | → [references\u002Fkubernetes.md](references\u002Fkubernetes.md) |\n| AWS Lambda (layer + env vars) | → [references\u002Faws-lambda.md](references\u002Faws-lambda.md) |\n| Azure VM \u002F VM Scale Set (VM extension) | → [references\u002Fazure-vm.md](references\u002Fazure-vm.md) |\n\n### By platform\n\nThe table above is organised by install mechanism, because that is what decides the procedure. If you are arriving from a particular cloud instead:\n\n| Platform | What you are deploying to | Go to |\n|---|---|---|\n| **AWS** | EC2 instance | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| | EKS — EC2 nodes | [kubernetes.md](references\u002Fkubernetes.md) |\n| | EKS — Fargate or Bottlerocket nodes | [kubernetes.md § AWS EKS specifics](references\u002Fkubernetes.md) — full-stack unavailable, `applicationMonitoring` only |\n| | Lambda function | [aws-lambda.md](references\u002Faws-lambda.md) |\n| **Azure** | VM or VM Scale Set | [azure-vm.md](references\u002Fazure-vm.md) |\n| | AKS | [kubernetes.md](references\u002Fkubernetes.md) — **not** the VM extension, even though node pools are VMSSes |\n| **Google Cloud** | GKE (standard) | [kubernetes.md](references\u002Fkubernetes.md) |\n| | GKE Autopilot | [kubernetes.md](references\u002Fkubernetes.md) for the operator path — full-stack is unavailable, as on Bottlerocket. Autopilot-specific tuning is not covered |\n| | Compute Engine VM | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) — the SSH procedure is not AWS-specific |\n| **On-prem \u002F anywhere else** | Linux or macOS you are logged into | below |\n| | Linux you reach over SSH | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| | Windows | [windows.md](references\u002Fwindows.md) |\n| | Kubernetes, or OpenShift via the standard operator | [kubernetes.md](references\u002Fkubernetes.md) — the classic OpenShift node-config-operator route is not covered |\n\n## VM \u002F server (Linux, macOS)\n\n**Endpoint** (substitute `${DT_ENV_URL_NORMALIZED}` and `${ARCH}` where `ARCH` ∈ `x86 | arm | ppc64le | s390`):\n\n```\nGET ${DT_ENV_URL_NORMALIZED}\u002Fapi\u002Fv1\u002Fdeployment\u002Finstaller\u002Fagent\u002Funix\u002Fdefault\u002Flatest?arch=${ARCH}&flavor=default\nHeader: Authorization: Api-Token ${DT_API_TOKEN}   # dt0c01.… access token\n        Authorization: Bearer ${DT_API_TOKEN}      # dt0s16.… platform token\n```\n\n**Install command:**\n\nSet the scheme to match your token — `Api-Token` for `dt0c01.…`, `Bearer` for `dt0s16.…`:\n\n```bash\nDT_AUTH=\"Api-Token ${DT_API_TOKEN}\"   # platform token: DT_AUTH=\"Bearer ${DT_API_TOKEN}\"\n\nwget -O Dynatrace-OneAgent-Linux.sh \\\n  --header=\"Authorization: ${DT_AUTH}\" \\\n  \"${DT_ENV_URL_NORMALIZED}\u002Fapi\u002Fv1\u002Fdeployment\u002Finstaller\u002Fagent\u002Funix\u002Fdefault\u002Flatest?arch=${ARCH}&flavor=default\"\n\nsudo \u002Fbin\u002Fsh Dynatrace-OneAgent-Linux.sh \\\n  --set-monitoring-mode=fullstack \\\n  --set-app-log-content-access=true \\\n  [--set-host-group=\u003Cname>] \\\n  [--set-network-zone=\u003Czone>]\n```\n\n**Restart caveat:** OneAgent cannot inject into already-running processes. After install, restart the workloads you want monitored.\n\n**Uninstall:**\n\n```bash\nsudo \u002Fopt\u002Fdynatrace\u002Foneagent\u002Fagent\u002Funinstall.sh\n```\n\nRemoves the systemd unit, `\u002Fopt\u002Fdynatrace`, and the `\u002Fetc\u002Fld.so.preload` line that injects the agent.\n\n---\n\n## When you should not use this skill\n\n- The user wants the install performed for them rather than explained. → This skill still applies: follow the target's procedure and run the commands, confirming the tenant first.\n- The user is asking why an install failed and wants an explanation. → This skill is appropriate.\n- The user wants a target this skill doesn't cover (Azure Functions \u002F App Service \u002F Container Apps, classic OpenShift node-config-operator, GKE Autopilot specifics, ECS Fargate). → Refer to \u003Chttps:\u002F\u002Fdocs.dynatrace.com>; this skill covers VM\u002Fserver, remote VM\u002FEC2 over SSH, Windows, Kubernetes and AWS Lambda.\n\n## References\n\n- OneAgent Linux install: \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fdynatrace-oneagent\u002Finstallation-and-operation\u002Flinux>\n- OneAgent Windows install: \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fdynatrace-oneagent\u002Finstallation-and-operation\u002Fwindows>\n- Kubernetes (Operator + DynaKube): \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fsetup-on-k8s\u002Fdeployment\u002Ffull-stack-observability>\n- Dynatrace Operator releases: \u003Chttps:\u002F\u002Fgithub.com\u002FDynatrace\u002Fdynatrace-operator\u002Freleases>\n- AWS Lambda (Hub): \u003Chttps:\u002F\u002Fwww.dynatrace.com\u002Fhub\u002Fdetail\u002Famazon-web-services-aws-lambda\u002F>\n","# Deploy Dynatrace OneAgent — knowledge reference\n\nThis skill is **reference-only**. It contains the documented endpoints, environment variables, token scopes, and commands that an operator (or another agent) needs to install OneAgent manually across the supported targets. It executes nothing.\n\n> This skill gives you the commands; it does not run them. Follow the procedure for the target you need, substituting the environment URL and token as documented below.\n\n## Hard rules for any agent consuming this skill\n\n- **Operate only on resources the user explicitly named.** Never create a placeholder\u002Ftest Lambda, IAM role, K8s namespace, secret, S3 bucket, EC2 instance, or any other fixture on your own initiative — not to \"demonstrate\", not \"while we're at it\", not preemptively. If the named resource doesn't exist and the user hasn't asked for it to be created, stop and ask. Side resources (additional Secrets Manager entries, monitoring, helper stacks) must not be provisioned silently — surface them as confirmation questions with the exact definition first.\n- **Explicit user-driven create modes are fine.** When the user passes `--create` (or explicitly says \"yes, create it\" after being asked), provisioning exactly the resources documented for that mode is the right thing to do — see *Create a new function and install OneAgent* in [references\u002Faws-lambda.md](references\u002Faws-lambda.md) for the documented set. Don't second-guess the function name the user typed: do **not** pattern-match on names like \"test\", \"demo\", \"scratch\", \"tmp\" and refuse, warn, or insist on an alternative. The input is authoritative; the rule above is about *silent* or *unsolicited* creation, not user-requested creation.\n- **Never persist the API token.** The token's only job is to (a) authenticate the OneAgent artifact download \u002F layer-ARN lookup and (b) get handed to the target system (Lambda env var or Secrets Manager, Linux installer, DynaKube secret) as part of the install. Do not cache it to local files, write it to scratch scripts, leave it in shell history, copy it into PR descriptions, or store it anywhere outside the target system that strictly needs it. Treat each run as fresh: supply via env var or 0600 file, use, discard.\n- **Never echo or log the API token.** When you have to reference it in a command, write `$DT_API_TOKEN` or an elided prefix (`dt0s16.…`, `dt0c01.…`). Don't paste the literal value into prose.\n- **Never assume the env URL, and confirm the tenant before installing.** Targeting the wrong environment fails *silently*: the install succeeds and the host or function simply reports to a tenant nobody is watching. An environment URL the user stated explicitly always wins over anything derived from a tool default or a previous run — never let a cached or discovered value override it. State the tenant you are about to use and let the user correct you. Tenant IDs (`abc12345`) and labs vs. prod determine the correct host.\n- **Writes that take a collection replace it — read, merge, then write.** Several APIs here accept a whole collection and overwrite whatever was there: `aws lambda update-function-configuration` does this for **both** `--environment` and `--layers`, so sending only the Dynatrace values silently deletes the function's own variables and any other layers. Always read current state, merge your additions into it, and write the union back. Take a rollback snapshot before the first write. This applies wherever you are about to replace a set rather than add to one.\n- **Deriving the env URL from dtctl.** `dtctl config current-context` returns only the *context name* (e.g. `my-env`), not a URL. The URL comes from `dtctl config describe-context \u003Cctx>`. Do **not** pipe that straight into `jq`: some dtctl versions ignore `-o json` and print a human table (`Environment:  https:\u002F\u002F…`) while still exiting 0, so jq dies on a parse error and takes any `set -e -o pipefail` script down with it. Check the output really is JSON first, and fall back to scraping the `Environment:` line:\n\n```bash\nCTX=\"$(dtctl config current-context 2>\u002Fdev\u002Fnull || true)\"\nOUT=\"$(dtctl config describe-context \"$CTX\" -o json 2>\u002Fdev\u002Fnull || true)\"\nif printf '%s' \"$OUT\" | jq -e . >\u002Fdev\u002Fnull 2>&1; then\n  DT_ENV_URL=\"$(printf '%s' \"$OUT\" | jq -r '.environment \u002F\u002F .url \u002F\u002F empty')\"\nelse\n  DT_ENV_URL=\"$(printf '%s' \"$OUT\" | awk 'tolower($1) ~ \u002F^(environment|url):$\u002F {print $2; exit}')\"\nfi\n```\n\n---\n\n## URL normalization\n\nDynatrace's \"new platform\" URLs and the classic OneAgent installer endpoints differ. Before constructing installer URLs, convert:\n\n| Input (Dynatrace UI \u002F docs)            | Use for installer endpoints           |\n|----------------------------------------|---------------------------------------|\n| `https:\u002F\u002F\u003Cid>.apps.dynatrace.com`      | `https:\u002F\u002F\u003Cid>.live.dynatrace.com`     |\n| `https:\u002F\u002F\u003Cid>.\u003Cregion>.apps.dynatracelabs.com` | `https:\u002F\u002F\u003Cid>.\u003Cregion>.dynatracelabs.com` |\n| Anything else                          | unchanged                             |\n\nThe tenant ID is the first dot-separated segment (`\u003Cid>`).\n\n---\n\n## Token types and the Authorization header\n\nTwo token families are in play, and **the `Authorization` scheme is chosen by the token's prefix, not by which endpoint you call**:\n\n| Token | Prefix | Header |\n|---|---|---|\n| Platform token | `dt0s16.` | `Authorization: Bearer \u003Ctoken>` |\n| Access token (classic API token) | `dt0c01.` | `Authorization: Api-Token \u003Ctoken>` |\n| PaaS token | `dt0s01.` | `Authorization: Bearer \u003Ctoken>` |\n| OAuth client secret | `dt0s02.` \u002F `dt0s03.` | ❌ not directly usable — must be exchanged for a bearer token first |\n\n**Platform tokens are the forward-looking default.** Dynatrace is deprecating access tokens: new tenants can no longer create them, and Classic API endpoints are being updated to accept platform tokens. Do **not** assume a token starts with `dt0c01.`. The reference implementation of this rule is dtwiz's `AuthHeader()` (`pkg\u002Finstaller\u002Finstaller.go`): `dt0c01.*` → `Api-Token`, everything else → `Bearer`.\n\nOne path hands the token to a component that has historically required a PaaS\u002Faccess token — if it rejects a platform token, use a `dt0c01.` access token there:\n\n- **Kubernetes** — the Dynatrace Operator authenticates using the `dynakube` secret.\n\nVM, remote VM\u002FEC2, Windows and Lambda call the Deployment API directly and work with either family.\n\n## Token scopes by target\n\nFor a **platform token** (`dt0s16.`), the OneAgent-relevant scopes live under **Fleet management**: `fleet-management:oneagents:download`, `fleet-management:oneagent.connection-info:read`, `fleet-management:oneagent.tokens:read`, `fleet-management:cluster-id:read`; Kubernetes additionally wants `fleet-management:activegates:download` and `fleet-management:activegate.tokens:create`. Generating the token via the Dynatrace **QuickStart** app provisions a working set.\n\nFor a **classic access token** (`dt0c01.`):\n\n| Target          | Required token scopes |\n|-----------------|------------------------|\n| VM \u002F Windows    | `InstallerDownload` (PaaS) |\n| Kubernetes      | `InstallerDownload`, `settings.read`, `settings.write`, `activeGateTokenManagement.create` — the Dynatrace UI's \"Kubernetes: Dynatrace Operator\" template sets all four. |\n| Azure VM \u002F VMSS | `InstallerDownload` (PaaS). Azure side: the caller's `az` identity needs `Contributor` or any role granting `Microsoft.Compute\u002F...\u002Fextensions\u002Fwrite` on the resource. |\n| AWS Lambda (runtime token) | A **connection auth token** consumed by the OneAgent layer at runtime. Distinct from the installer token. Create from the Dynatrace UI under *Access tokens* with `entities.read`, or use the Hub → AWS Lambda template. |\n\nTokens are never username-scoped — they belong to the tenant.\n\n---\n\n## Targets\n\nEach target has its own reference. They share the rules, URL normalization and token guidance above — read those first, then the one you need.\n\nManaged Kubernetes distributions are covered inside the Kubernetes reference rather than separately: the install is identical and only the node type differs, so the deltas belong next to the procedure they modify.\n\n| Target | Reference |\n|---|---|\n| VM \u002F server (Linux, macOS) | below — the base case every other target builds on |\n| Remote VM \u002F EC2 over SSH | → [references\u002Fremote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| Windows host (WSL or native) | → [references\u002Fwindows.md](references\u002Fwindows.md) |\n| Kubernetes (Operator + DynaKube) — incl. **EKS**, Fargate and Bottlerocket limits | → [references\u002Fkubernetes.md](references\u002Fkubernetes.md) |\n| AWS Lambda (layer + env vars) | → [references\u002Faws-lambda.md](references\u002Faws-lambda.md) |\n| Azure VM \u002F VM Scale Set (VM extension) | → [references\u002Fazure-vm.md](references\u002Fazure-vm.md) |\n\n### By platform\n\nThe table above is organised by install mechanism, because that is what decides the procedure. If you are arriving from a particular cloud instead:\n\n| Platform | What you are deploying to | Go to |\n|---|---|---|\n| **AWS** | EC2 instance | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| | EKS — EC2 nodes | [kubernetes.md](references\u002Fkubernetes.md) |\n| | EKS — Fargate or Bottlerocket nodes | [kubernetes.md § AWS EKS specifics](references\u002Fkubernetes.md) — full-stack unavailable, `applicationMonitoring` only |\n| | Lambda function | [aws-lambda.md](references\u002Faws-lambda.md) |\n| **Azure** | VM or VM Scale Set | [azure-vm.md](references\u002Fazure-vm.md) |\n| | AKS | [kubernetes.md](references\u002Fkubernetes.md) — **not** the VM extension, even though node pools are VMSSes |\n| **Google Cloud** | GKE (standard) | [kubernetes.md](references\u002Fkubernetes.md) |\n| | GKE Autopilot | [kubernetes.md](references\u002Fkubernetes.md) for the operator path — full-stack is unavailable, as on Bottlerocket. Autopilot-specific tuning is not covered |\n| | Compute Engine VM | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) — the SSH procedure is not AWS-specific |\n| **On-prem \u002F anywhere else** | Linux or macOS you are logged into | below |\n| | Linux you reach over SSH | [remote-vm-ec2.md](references\u002Fremote-vm-ec2.md) |\n| | Windows | [windows.md](references\u002Fwindows.md) |\n| | Kubernetes, or OpenShift via the standard operator | [kubernetes.md](references\u002Fkubernetes.md) — the classic OpenShift node-config-operator route is not covered |\n\n## VM \u002F server (Linux, macOS)\n\n**Endpoint** (substitute `${DT_ENV_URL_NORMALIZED}` and `${ARCH}` where `ARCH` ∈ `x86 | arm | ppc64le | s390`):\n\n```\nGET ${DT_ENV_URL_NORMALIZED}\u002Fapi\u002Fv1\u002Fdeployment\u002Finstaller\u002Fagent\u002Funix\u002Fdefault\u002Flatest?arch=${ARCH}&flavor=default\nHeader: Authorization: Api-Token ${DT_API_TOKEN}   # dt0c01.… access token\n        Authorization: Bearer ${DT_API_TOKEN}      # dt0s16.… platform token\n```\n\n**Install command:**\n\nSet the scheme to match your token — `Api-Token` for `dt0c01.…`, `Bearer` for `dt0s16.…`:\n\n```bash\nDT_AUTH=\"Api-Token ${DT_API_TOKEN}\"   # platform token: DT_AUTH=\"Bearer ${DT_API_TOKEN}\"\n\nwget -O Dynatrace-OneAgent-Linux.sh \\\n  --header=\"Authorization: ${DT_AUTH}\" \\\n  \"${DT_ENV_URL_NORMALIZED}\u002Fapi\u002Fv1\u002Fdeployment\u002Finstaller\u002Fagent\u002Funix\u002Fdefault\u002Flatest?arch=${ARCH}&flavor=default\"\n\nsudo \u002Fbin\u002Fsh Dynatrace-OneAgent-Linux.sh \\\n  --set-monitoring-mode=fullstack \\\n  --set-app-log-content-access=true \\\n  [--set-host-group=\u003Cname>] \\\n  [--set-network-zone=\u003Czone>]\n```\n\n**Restart caveat:** OneAgent cannot inject into already-running processes. After install, restart the workloads you want monitored.\n\n**Uninstall:**\n\n```bash\nsudo \u002Fopt\u002Fdynatrace\u002Foneagent\u002Fagent\u002Funinstall.sh\n```\n\nRemoves the systemd unit, `\u002Fopt\u002Fdynatrace`, and the `\u002Fetc\u002Fld.so.preload` line that injects the agent.\n\n---\n\n## When you should not use this skill\n\n- The user wants the install performed for them rather than explained. → This skill still applies: follow the target's procedure and run the commands, confirming the tenant first.\n- The user is asking why an install failed and wants an explanation. → This skill is appropriate.\n- The user wants a target this skill doesn't cover (Azure Functions \u002F App Service \u002F Container Apps, classic OpenShift node-config-operator, GKE Autopilot specifics, ECS Fargate). → Refer to \u003Chttps:\u002F\u002Fdocs.dynatrace.com>; this skill covers VM\u002Fserver, remote VM\u002FEC2 over SSH, Windows, Kubernetes and AWS Lambda.\n\n## References\n\n- OneAgent Linux install: \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fdynatrace-oneagent\u002Finstallation-and-operation\u002Flinux>\n- OneAgent Windows install: \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fdynatrace-oneagent\u002Finstallation-and-operation\u002Fwindows>\n- Kubernetes (Operator + DynaKube): \u003Chttps:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fingest-from\u002Fsetup-on-k8s\u002Fdeployment\u002Ffull-stack-observability>\n- Dynatrace Operator releases: \u003Chttps:\u002F\u002Fgithub.com\u002FDynatrace\u002Fdynatrace-operator\u002Freleases>\n- AWS Lambda (Hub): \u003Chttps:\u002F\u002Fwww.dynatrace.com\u002Fhub\u002Fdetail\u002Famazon-web-services-aws-lambda\u002F>\n",{"name":5,"license":15,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill dt-setup-oneagent",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill dt-setup-oneagent",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill dt-setup-oneagent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002FSKILL.md",true,[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Faws-lambda.md","REFERENCE","参考文档",13387,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002Freferences\u002Faws-lambda.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fazure-vm.md",8186,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002Freferences\u002Fazure-vm.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fkubernetes.md",6448,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002Freferences\u002Fkubernetes.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fremote-vm-ec2.md",5027,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002Freferences\u002Fremote-vm-ec2.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fwindows.md",1452,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-setup-oneagent\u002Freferences\u002Fwindows.md",[70,77,84,90,97,104],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":85,"name":79,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]