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: content/en/tracing/live_debugger/_index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,9 +148,9 @@ Live Debugger data might contain sensitive information, especially when using th
148
148
1. Use the built-in [sensitive data scrubbing][1] mechanisms.
149
149
2. Use [Sensitive Data Scanner][17] to identify and redact sensitive information based on regular expressions.
150
150
151
-
### Debug with Bits
151
+
### Bits Live Debugger
152
152
153
-
[Debug with Bits][23] lets you investigate a running service by describing the issue in plain language. Bits Code handles logpoint placement, captures variable snapshots, and helps interpret the results.
153
+
[Bits Live Debugger][23] lets you investigate a running service by describing the issue in plain language. Bits Code handles logpoint placement, captures variable snapshots, and helps interpret the results.
154
154
155
155
## Impact on performance and billing
156
156
@@ -195,4 +195,4 @@ The following constraints apply to Live Debugger usage and configuration:
Debug with Bits is in Preview. Request access to join the waiting list.
19
+
Bits Live Debugger is in Preview. Request access to join the waiting list.
18
20
{{< /beta-callout >}}
19
21
20
22
## Overview
21
23
22
-
Debug with Bits brings a conversational interface to Live Debugger for investigating running services through natural language. Describe what you want to investigate, and Bits places logpoints, retrieves variable snapshots, and interprets results. After Bits identifies a root cause, it can suggest code fixes.
24
+
Bits Live Debugger brings a conversational interface to Live Debugger for investigating running services through natural language. Describe what you want to investigate, and Bits places logpoints, retrieves variable snapshots, and interprets results. After Bits identifies a root cause, it can suggest code fixes.
23
25
24
26
All debugging activity runs through [Live Debugger][1], so the same [permissions][2], rate limits, auto-expiry behavior, and [sensitive data scrubbing][3] apply.
25
27
26
28
<divclass="alert alert-info">
27
-
Debug with Bits uses <ahref="/bits_ai/bits_ai_dev_agent/">Bits Code</a>, which may impact billing.
29
+
Bits Live Debugger uses <ahref="/bits_ai/bits_ai_dev_agent/">Bits Code</a>, which may impact billing.
28
30
</div>
29
31
30
32
## Prerequisites
31
33
32
-
Before using Debug with Bits:
34
+
Before using Bits Live Debugger:
33
35
34
36
-[Live Debugger][1] must be enabled for the target service. See [Requirements and setup][7] for details.
35
37
- Your account must have the [permissions][2] required to use Live Debugger, including read, write, and variable-capture permissions for the target environment.
@@ -53,7 +55,7 @@ Logpoints created by Bits follow the same rules as manually created logpoints. T
53
55
## Start a debugging session
54
56
55
57
1. Go to [Live Debugger][4] in Datadog.
56
-
1. In the Debug with Bits chatbox, describe the issue you want to investigate. Select the target service and environment before submitting the prompt.
58
+
1. In the Bits Live Debugger chatbox, describe the issue you want to investigate. Select the target service and environment before submitting the prompt.
57
59
58
60
Bits then works through the investigation automatically:
59
61
- It analyzes relevant code paths in the connected source code repository and may ask follow-up questions to form a hypothesis.
0 commit comments