Manage Environments, Tags, and Component Webhooks

Before you start

• Decide which environments responders should use consistently.
• Decide which labels deserve a reusable tag instead of free-form typing.

Do this

1. In Catalog, create the environments people will choose during incident declaration and alert routing.
2. Mark the default environment you want the workspace to prefer.
3. Create reusable tags for labels that should stay consistent across incidents and alerts.
4. Open a system or function overview and review its component webhook if you want to point a monitoring rule directly at that catalog object.
5. Copy the component webhook URL only for sources that should always route to that specific system or function.

Check it worked

• Environments are available in incident and alert flows.
• Tags are reusable instead of being retyped differently each time.
• Component webhooks route directly to the intended catalog object.

If it does not work

• If environment names are confusing, fix them before teams start relying on them.
• If tags drift in meaning, remove or rename them instead of adding close variants.
• If a component webhook routes to the wrong place, verify you copied the right system or function URL.

Next

• Link PagerDuty services
• Create a webhook source