Source
Alerting, integrations & developer workflow — found from sitemap — Raygun
Checked for Raygun on 6 Nov 2026
- Page
- https://raygun.com/documentation/product-guides/apm/raygun-cli/
- Checked
- 6 Nov 2026, 04:23 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9ef7f43a657eb89be71908782193b1246157980979362ecc56dc9e0a247b79d5
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Apm3 cli Report an error
“Raygun APM 3.x includes a secure command line in the installed RaygunAgent.exe. Use it to inspect Agent health and configure running IIS or supported .NET processes when the Configuration Utility cannot be used, including Windows Server Core.”
-
Rgc removed Report an error
“Warning: Raygun APM 3.x does not ship the retired rgc.exe. Do not use old rgc -register, rgc -enable, rgc -profile, diagnostic, or Agent-tail commands with a current installation.”
-
Cli admin required Report an error
“Run mutating commands from an elevated Administrator prompt. The RaygunAgent service must be running.”
-
Cli status json Report an error
“& $agent status --json”
-
Cli app discover Report an error
“& $agent app discover --web-only --json”
-
Cli register enable Report an error
“& $agent app register --process-id 1234 & $agent app enable --process-id 1234”
-
Cli API key no arg Report an error
“The API key is deliberately not accepted as a command argument or environment variable.”
-
Cli API key stdin Report an error
“Store exactly one line in an ACL-protected local file or retrieve it from the host's secret provider, then pipe it through standard input”
-
Cli iis recycle Report an error
“Enabling an IIS target recycles its application pool by default so the new worker loads the profiler and, for CoreCLR, the startup hook.”
-
Cli shared pool flag Report an error
“Use --allow-shared-pool only when every application in the pool should use the same Raygun API key”
-
Cli coreclr hook Report an error
“For CoreCLR targets, enabling also adds the stable Raygun path to DOTNET_STARTUP_HOOKS while preserving non-Raygun startup-hook entries.”
-
Cli settings export import Report an error
“& $agent settings export --output C:\Protected\raygun-apm-settings.json & $agent settings export --output C:\Protected\raygun-apm-settings.json --overwrite & $agent settings import --input C:\Protected\raygun-apm-settings.json”
-
Cli exit codes Report an error
“Exit code Meaning 0 The requested state is satisfied. 2 Command syntax or an argument is invalid. 10 The local Agent service is unavailable. 11 The process or settings file was not found. 12 The input or runtime is unsupported. 13 Registration, shared-pool, or overwrite conflict. 14 Administrator or local management authorization failed. 20 The operation failed without a safe successful result. 21 State changed, but a follow-up action such as an IIS recycle failed.”
-
Cli json changed flag Report an error
“With --json, use changed to distinguish a new change from an idempotent no-op.”
-
Cli export warning Report an error
“Exported settings contain protected application information. Keep the file on a local, access-controlled path.”
Scores citing this record
- The Mobile Team Lead Alerting, integrations & developer workflow
- The SaaS CTO Alerting, integrations & developer workflow
- The Skeptic Alerting, integrations & developer workflow
- The Site Reliability Engineer Alerting, integrations & developer workflow