4
Update Beacon extraction rules to drop events rather than update all
- Live
|
M |
Marc Farrow |
Beacons can be configured to auto-extract the component name from the incoming payload. Unfortunately, the beacon's default behaviour is to update ALL components if the rules cannot match the oncoming payload to an existing component.
This is not our desired behaviour, and could cause panic amongst our subscribers.
Instead, can another option be added to DROP events rather than update ALL components?
A workaround is to create a CATCHALL service, but if the beacon auto-creates incidents, this is not ideal, as it'll show on our statuspage.
Activity Newest / Oldest
Customer Success
This went live in Q4 2023
Customer Success
Status changed to: Live
Customer Success
Status changed to: Planned
Customer Success
Stop Processing rule being added to late Q4 2023/early Q12024
Evan Raines
Status changed to: Under review
Evan Raines
Thank you for submitting a request. I have brought this internally for review.