Event forwarding #1371
Merged
Event forwarding #1371
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phil-snowplow
added
the
do not merge
✅ Deploy Preview for snowplow-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
re Should we break out Error handling and troubleshooting into its own page? yeah I find it a bit odd to have this section so prominently on the main landing page. A separate page would be good - and consistent with the GTM SS section that has a Testing and debugging page |
mscwilson
reviewed
Aug 26, 2025
mscwilson
reviewed
Sep 10, 2025
| - **Failure timestamp**: when the error occurred | ||
| - **Transformation state**: data state at the point of failure | ||
|
|
||
| ### Querying failed event logs |
There was a problem hiding this comment.
is this section AWS only?
There was a problem hiding this comment.
yes, for now. added a callout mentioning that and a todo to add steps for GCP
There was a problem hiding this comment.
Ticket here - but Phil no objection to you translating them if you'd prefer get it done before we can get to it :)
docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md
Outdated
Show resolved
Hide resolved
docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md
Outdated
Show resolved
Hide resolved
docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md
Outdated
Show resolved
Hide resolved
docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md
Outdated
Show resolved
Hide resolved
docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md
Show resolved
Hide resolved
more updates
commit 9116f4c Author: spenes <[email protected]> Date: Tue Sep 16 15:48:40 2025 +0300 Enrich 6.1.1 commit eddc40e Author: Nick <[email protected]> Date: Mon Sep 15 12:26:26 2025 +0100 Add info on running Micro as a jar (#1407) commit 314e37a Author: Nick <[email protected]> Date: Fri Sep 12 17:22:56 2025 +0100 Update index.md commit 6707f4b Author: jborlase-snowplow <[email protected]> Date: Fri Sep 12 17:55:30 2025 +0200 Removing redundant Snowtype page in GTM (#1405) commit 7de4d8c Author: jborlase-snowplow <[email protected]> Date: Fri Sep 12 16:59:07 2025 +0200 Updating Snowtype overview page (#1403) * updating Snowtype page * fixing casing * Update docs/data-product-studio/snowtype/index.md Co-authored-by: Nick <[email protected]> --------- Co-authored-by: Nick <[email protected]> commit 7f3a45b Author: Nick <[email protected]> Date: Fri Sep 12 15:57:11 2025 +0100 Add new dedicated pages for warehouses and lakes (#1402) * Add new dedicated pages for warehouses and lakes * Added a page per each warehouse and lake with key details * Explicitly listed the required permissions * Added a simplified description of the Snowplow data format for each * Moved detailed schema reference to API reference section * Removed mentions of Postgres (and some of Synapse) to avoid confusion * Rephrase prerequisites to heads up * Address review comments * Add lake maintenance jobs commit c08d0aa Author: spenes <[email protected]> Date: Fri Sep 12 17:05:47 2025 +0300 Databricks Streaming Loader 0.2.0 commit 96daedc Author: Phil Catterall <[email protected]> Date: Thu Sep 11 13:15:17 2025 -0400 fix margin to adjust for grid (#1396) * fix margin to adjust for grid * fix table and list margins * forgot about ordered lists commit c024007 Author: Nick <[email protected]> Date: Thu Sep 11 11:39:58 2025 +0100 No 🍪 in my 🖨️ please (#1400)
phil-snowplow
removed
the
do not merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft PR for new Event Forwarding documentation.
Overview of changes
New event forwarding documentation structure:
New component:
Open questions
This change introduces some inconsistency between the Event Forwarding and warehouse/lake loaders sections: all the details for specific loaders are in API Reference, but for Event Forwarding I'm proposing we bring them up to the main sectionRESOLVEDShould we kill the custom integrations page? Or mark as deprecated? AFAIK, we don't want customers to read directly off the enriched stream anymore.DECISION: leave as is until we support more destinations.Should we break out Error handling and troubleshooting into its own page?DECISION: yesStill to do
/docs/fundamentals/destinations/section to reflect the changes abovedeprecateddocs/api-reference/failed-events/index.mdwith new event forwarding failure type