You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/unify/debugger.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,18 @@ redirect_from:
7
7
8
8
The Profile Source Debugger enables you to inspect and monitor events that Segment sends downstream
9
9
10
-
Because Segment generates a unique Source for every Destination connected to a Space, the Debugger gives you insight into how Segment sends events before they reach their Destination. This automatically generated source cannot be deleted and should not be disabled even when the destination is removed, in order for Segment to function as designed. The source will be reused by Segment as needed.
10
+
Because Segment generates a unique source for every destination connected to a Space, the Debugger gives you insight into how Segment sends events before they reach their destination. Even when a destination is removed, you can't delete and shouldn't disable this source for Segment to function as designed. The source will be reused by Segment as needed.
11
11
12
-
The Debugger provides you with the payload information you need to troubleshoot potential formatting issues and ensure Segment sends events as your Destinations expect.
12
+
The Debugger provides you with the payload information you need to troubleshoot potential formatting issues and ensure Segment sends events as your destinations expect.
13
13
14
14
## Working with the Debugger
15
-
16
-
Navigate to the Debugger tab on the Unify settings page of the space you want to debug. Select the Source you want to inspect in the Debugger.
15
+
16
+
Navigate to the Debugger tab on the Unify settings page of the space you want to debug. Select the source you want to inspect in the Debugger.
17
17
18
18
The Debugger presents a stream of incoming events. The event inspector displays three tabs for each event:
19
19
20
-
***Pretty view** shows the actual API call Segment sends to your Destination.
21
-
***Raw view** shows the full JSON object Segment sends to your Destination from the calls you sent, including timestamps, properties, traits, and ids.
20
+
***Pretty view** shows the actual API call Segment sends to your destination.
21
+
***Raw view** shows the full JSON object Segment sends to your destination from the calls you sent, including timestamps, properties, traits, and ids.
22
22
***Violations** displays any violations triggered by the event.
23
23
24
24
Similar to the Connections Debugger, you can search through events using information contained within the event's payload.
0 commit comments