Skip to content

Commit c3b3ce4

Browse files
authored
Merge pull request #5561 from segmentio/bobbyatsegment-patch-14
Add note on event order in debugger
2 parents 811989f + 49345ed commit c3b3ce4

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

src/connections/sources/debugger.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ title: Using the Source Debugger
44

55
The Source Debugger is a real-time tool that helps you confirm that API calls made from your website, mobile app, or servers arrive to your Segment Source, so you can troubleshoot your Segment set up even quicker. With the Debugger, you can check that calls are sent in the expected format without having to wait for any data processing.
66

7+
> info ""
8+
> The Source Debugger's event order may not reflect how events send downstream or are received by connected destinations. The Debugger primarily confirms incoming data and provides a basic view of its structure. For a reliable record of the data you send to Segment, Segment advises you to attach a raw storage destination to your sources.
9+
710
![A screenshot of the debugger view, with a Track event selected and the pretty view opened.](images/debugger_view.png)
811

912
The Debugger is separate from your workspace's data pipeline and is not an exhaustive view of all the events ever sent to your Segment workspace. The Debugger only shows a sample of the events that the Source receives in real time, with a cap of 500 events. The Debugger is a great way to test specific parts of your implementation to validate that events are being fired successfully and arriving to your Source.

0 commit comments

Comments
 (0)