Uptime Monitoring: Settings

Overview

Use this page to manage uptime check environments and outgoing IP addresses. An environment is a label, such as Production or Acceptance, used to group uptime checks by the tier of infrastructure they monitor; a check can only use an environment that appears on this page. An outgoing address is an IPv4 or IPv6 address or CIDR range that identifies traffic from this appliance when it runs checks; customers add these addresses to their firewall allow list so the appliance's checks can reach their systems.

Both lists feed Uptime Monitoring: Checks, where a check can only be tagged with an environment that appears in the Environments table, and where the addresses you save here are shown to the customer on each check's Connection step. The Environments table starts out populated from whatever environments your existing checks already used, so this page is often visited after checks exist rather than before the first one is created.

From here you add, rename, or remove environment labels, and you detect, edit, and save the outgoing addresses that checks use when calling out to customer systems.

Key concepts

• environment - A label, such as Production or Acceptance, used to group uptime checks by the tier of infrastructure they monitor. A check can only use an environment that appears in this list. (related: Uptime Monitoring: Checks)
• outgoing address - An IPv4 or IPv6 address or CIDR range that identifies traffic originating from this appliance when it runs uptime checks. Customers allow these addresses through their firewalls. (related: Uptime Monitoring: Checks)
• check - A configured uptime monitor that is tagged with one environment from this page and whose Connection step displays the outgoing addresses saved here. (related: Uptime Monitoring: Checks)

When to use it

• Adding a new environment label (for example Acceptance or Staging) before creating or editing checks that need it.
• Answering a customer's question about which IP addresses to allow through their firewall for uptime checks.
• Refreshing the published outgoing addresses after the appliance's network egress changes.
• Cleaning up environment labels that no longer correspond to a real tier of checks.
• Checking how many checks use an environment before deleting it.

Before you begin

• Know which environment labels your checks already use, since the Environments table starts out populated from the environments your existing checks in Uptime Monitoring: Checks already reference.
• Have the appliance's actual outgoing IPv4/IPv6 addresses or CIDR ranges on hand if you plan to add or correct entries rather than rely on Detect.
• Sign in with an account that has access to Uptime Monitoring settings.

Common workflows

Add a new environment for checks

Persona: Load-test operator

1. Type a descriptive name into the New environment field.
   • Expect: The field accepts the text up to 64 characters; no row is created yet.
2. Select Add.
   • Expect: A new row appears in the Environments table with the typed name and 0 checks.

Verify: The new environment name is listed in the Environments table and can now be selected when tagging a check in Uptime Monitoring: Checks.

Publish the appliance's outgoing addresses

Persona: Admin

1. Select Detect in the Outgoing addresses panel.
   • Expect: The appliance's current outgoing address is added to the Addresses field.
2. Edit the Addresses field to add or remove addresses or CIDR ranges, one per line, up to 20 entries.
   • Expect: The field reflects the edited list and the counter beside it updates.
3. Select Save.
   • Expect: The address list is persisted.

Verify: Opening any check's Connection step shows the same addresses just saved, which is what you hand the customer for their firewall allow list.

Steps

Step 1

Open Settings under Monitoring and Uptime.

Expected result: The Uptime Settings page opens showing the Environments panel on the left, listing Production with 2 checks, and the Outgoing addresses panel on the right, with the Addresses field already listing two entries.

This is the entry point for defining which environments checks can use and which addresses customers must allow through their firewalls.

• The Environments panel lists each environment's Name and Checks count.
• The Outgoing addresses panel shows the Addresses field with a counter against a 20-address maximum.

Field reference

Column reference

Controls reference

Add

Creates a new environment using the name typed into the New environment field and adds it as a row in the Environments table.

When to use: After typing a new environment name that checks should be able to use.

Side effects: Mutating: immediately adds a new row with 0 checks to the Environments table.

Edit

Opens the environment name on this row for inline editing.

When to use: To correct or rename an existing environment label.

Side effects: Mutating: changes the stored environment name once confirmed.

Delete

Removes the environment from the list.

When to use: When an environment tier is retired and no check needs it anymore.

Side effects: Mutating and destructive: removes the row. If the Checks column shows a non-zero count, the environment is still referenced, so remove it with care.

Detect

Probes the appliance's current outgoing network connection and fills the Addresses field with the detected address.

When to use: When you are unsure what address the appliance currently uses to call out, or after a network change.

Side effects: Updates the Addresses field only; nothing is persisted until you select Save.

Save

Persists the current contents of the Addresses field.

When to use: After adding, editing, removing, or detecting outgoing addresses.

Side effects: Mutating: writes the address list that is then shown to customers on each check's Connection step.

Verify the result

Uptime Settings loads with the Environments panel on the left and the Outgoing addresses panel on the right. The Environments table lists every environment currently available to checks, each with a Checks count showing how many checks reference it, and the Addresses field lists the IP addresses and CIDR ranges customers are told to allow through their firewalls. If a newly added environment does not appear when assigning a check in Uptime Monitoring: Checks, return to this page and confirm the row is present in the Environments table. If an address change is not reflected on a check's Connection step, confirm Save was selected after the edit.

Troubleshooting

• Symptom: A newly typed environment name does not appear in the table after selecting Add. Fix: Confirm the name is 64 characters or fewer; retype a shorter name and select Add again.
• Symptom: The environment you want to delete still shows a Checks count above zero. Fix: Reassign or remove those checks in Uptime Monitoring: Checks first, since the environment stays in use until no check references it.
• Symptom: The Addresses field already lists 20 entries and a new line will not save. Fix: Remove an existing address or CIDR range before adding a new one; the field caps at 20 entries.
• Symptom: Selecting Detect does not change the Addresses field. Fix: Check the appliance's network connection; Detect reports what the appliance can currently see as its outgoing address, so it has nothing to add if the appliance cannot reach the network.
• Symptom: Addresses edited here do not show up on a check's Connection step. Fix: Select Save after editing the Addresses field; unsaved edits are not shown anywhere else.

Related articles

• Next step: Uptime Monitoring: Checks - environments and addresses defined here are assigned to and shown on individual checks
• See also: Infrastructure: Appliance - outgoing addresses originate from this appliance's network connection