Skip to content

Update Violation Forwarding Information to include Actions Destinations #4033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 17, 2023
Merged

Update Violation Forwarding Information to include Actions Destinations #4033

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2c43b17
Update faq.md
ashton-huxtable Jan 11, 2023
c8d25ad
Apply suggestions from code review
forstisabella Jan 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/protocols/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,15 @@ You can subscribe to a variety of Protocols specific alerts through the workspac

### How can I get notified when someone makes a change to my tracking plan?

You can forward notifications from Protocols to a new Segment Source, which can then send them to notification tools such as Slack webhook.
You can forward notifications from Protocols to a new Segment source, which can then send them to notification tools such as Slack webhook.

You can also forward these Protocols alerts to any (cloud-mode) Segment destination that accepts Track calls, including data warehouses. Most customers record these activity feed events to a data warehouse for analysis.

### How do I get notified when new violations are generated? Can I create custom violation notifications?

You can enable [violation event forwarding](/docs/protocols/validate/forward-violations/) to start delivering violations as Track calls to a Segment Source. From there, you can forward the events to any Segment destination that accepts Track calls.
You can enable [violation event forwarding](/docs/protocols/validate/forward-violations/) to start delivering violations as Track calls to a Segment source. From there, you can forward the events to any Segment destination that accepts Track calls.

You can also use the Slack Actions destination to set event triggers for context fields, meaning events with violations are sent as Track calls directly from the source.


## Protocols Tracking Plan
Expand Down