doctl monitoring uptime alert get
Generated on 9 Apr 2025
from doctl version
v1.124.0
Usage
doctl monitoring uptime alert get <uptime-check-id> <uptime-alert-id> [flags]Aliases
gDescription
Retrieves information about an uptime alert policy.
Example
The following example retrieves the configuration for an alert policy with the ID 418b7972-fc67-41ea-ab4b-6f9477c4f7d8 that is a policy of an uptime check with the ID f81d4fae-7dec-11d0-a765-00a0c91e6bf6:
doctl monitoring uptime alert get f81d4fae-7dec-11d0-a765-00a0c91e6bf6 418b7972-fc67-41ea-ab4b-6f9477c4f7d8Flags
| Option | Description |
|---|---|
--format |
Columns for output in a comma-separated list. Possible values: ID, Name, Type, Threshold, Comparison, Period, Emails, Slack Channels. |
--help, -h |
Help for this command |
--no-header |
Return raw data with no headers Default: false |
Related Commands
| Command | Description |
|---|---|
| doctl monitoring uptime alert | Display commands to manage uptime alerts |
Global Flags
| Option | Description |
|---|---|
--access-token, -t |
API V2 access token |
--api-url, -u |
Override default API endpoint |
--config, -c |
Specify a custom config file Default: |
--context |
Specify a custom authentication context name |
--http-retry-max |
Set maximum number of retries for requests that fail with a 429 or 500-level error
Default: 5 |
--http-retry-wait-max |
Set the minimum number of seconds to wait before retrying a failed request
Default: 30 |
--http-retry-wait-min |
Set the maximum number of seconds to wait before retrying a failed request
Default: 1 |
--interactive |
Enable interactive behavior. Defaults to true if the terminal supports it (default false)
Default: false |
--output, -o |
Desired output format [text|json] Default: text |
--trace |
Show a log of network activity while performing a command Default: false |
--verbose, -v |
Enable verbose output Default: false |