Keep address-service context attached to the resource
When an address-check process sends useful context, have Notis add it to the related Better Stack resource as metadata.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Metadata
Creates or updates resource metadata, replacing the existing value for the same key.
Why this helps
Responders lose time when service ownership or address-check context is separated from the resource they are investigating.
- Keep supplied context near the relevant Better Stack resource.
- Make service details easier to find during investigation.
- Avoid repeatedly entering the same metadata by hand.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Better Stack once in the Notis portal.
- 2Create an automation by telling Notis which supplied address-service context to add as metadata to the referenced resource.
- 3Pick the Notis webhook trigger and have your existing process send the resource reference and context to its HTTP endpoint.
- 4Choose where Notis should send run reports.
- 5Test with one real resource and context value.
Questions about this workflow
What resource details should the webhook include?
Include the resource reference and the metadata key and value you want applied. Better Stack replaces an existing value for the specified key.
Can this infer service ownership from Addresszen?
Only if your existing process supplies that information in the webhook request. No Addresszen trigger event or ownership data is specified here.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Better stack. A trigger fires from one place; an action lands in another.
Addresszen triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Creates an incident escalation policy that defines who is notified and when.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Acknowledge Incident
Acknowledges an active incident, stopping further escalations.
Create Heartbeat Group
Creates a group to organize related heartbeat checks.
Create Outgoing Webhook Integration
Creates an integration to send event notifications to an endpoint.
Create Heartbeat
Creates a heartbeat monitor that checks for regular signals from a service.
Create Source Group
Creates a group to organize related log sources.
Delete Escalation Policy
Permanently deletes an escalation policy.
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Connect any two apps with Notis in the middle.
Addresszen and Better stack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Better stack.