jaeger-clilisted

# Jaeger CLI Skill Use the instance and rules below when constructing all Jaeger API commands. ## Instances Update the table below with your Jaeger Query instance URLs before using this skill: | Environment | Base URL | Token File (if auth is enforced) | |---|---|---| | Production | `https://<your-jaeger-prod-url>` | `~/.jaeger/prod.token` | | Staging | `https://<your-jaeger-staging-url>` | `~/.jaeger/staging.token` | If the target instance is unclear, ask the user before running any command. ## Prerequisites (one-time setup by user) If the Jaeger instance is behind an authentication proxy, obtain a token and save it to the corresponding token file (see instance table above). Never print or display token values. Do not perform these steps yourself. ```bash mkdir -p ~/.jaeger && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE> ``` ## Command Format All API calls use `curl` against the Jaeger Query Service API: ```bash curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \ "<BASE_URL>/api/<endpoint>" | jq . ``` If the instance has no auth in front of it, omit the `Authorization` header entirely. Example (production): ```bash curl -s -H "Authorization: Bearer $(cat ~/.jaeger/prod.token)" \ "https://<your-jaeger-prod-url>/api/services" | jq . ``` ## Available API Endpoints ### Read-only (safe, no confirmation needed) | Endpoint | Description | |---|---| | `/api/services` | List all known service names | | `/api/services/<service>/operations`