Skip to content

Commit 5432380

Browse files
authored
Merge pull request #4685 from segmentio/tanjinhong72-patch-2
Added information that the Engage generated source should not be disabled
2 parents 0b99f46 + 491dd65 commit 5432380

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/unify/debugger.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,18 @@ redirect_from:
77

88
The Profile Source Debugger enables you to inspect and monitor events that Segment sends downstream
99

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 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.
1111

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.
1313

1414
## 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.
1717

1818
The Debugger presents a stream of incoming events. The event inspector displays three tabs for each event:
1919

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.
2222
* **Violations** displays any violations triggered by the event.
2323

2424
Similar to the Connections Debugger, you can search through events using information contained within the event's payload.

0 commit comments

Comments
 (0)