Conversation
| - `loops`: The route parameter hardcoded to `5` | ||
| - `myString`: A string `"Hello, world!"` | ||
| - `mySequence`: An array of integers `[1, 2, 3]` | ||
| - `mySequence`: An array of integers `[1, 2, 3, 4]` |
There was a problem hiding this comment.
such a small nit, but the agents are annoyed: we reference mySequence[3] but then give a len == 3 sequence so thats an out of bounds.
| | `@duration` | Provides access to the method call execution duration, as a floating-point value in milliseconds. | | ||
| | `@exception`| Provides access to the exception thrown within the method (only available if an uncaught exception exists). | | ||
| | `@it` | Provides access to the current element during collection iteration. Used in predicates for list operations. | | ||
| | `@key` | Provides access to the current key during dictionary iteration. Used in predicates for dictionary operations. | |
There was a problem hiding this comment.
this was never fully completed, so we currently reject them in all [maybe most?] cases
|
|
||
| Live Debugger uses logpoints: auto-expiring, non-breaking breakpoints that collect diagnostic data without pausing the application. Since execution continues normally, Live Debugger can be used safely on production systems to investigate problems as they happen. | ||
|
|
||
| Live Debugger complements [Dynamic Instrumentation][38], which adds metrics, spans, and span tags using the same [expression language][15]. |
There was a problem hiding this comment.
@timsee To improve the agent's understanding of DI vs. LD, does the explanation need to be in the intro section? Or could we have a dedicated section lower on the page with a more detailed explanation of how they overlap and differ?
There was a problem hiding this comment.
yeah, lets move out of the intro do a dedicated section, thats a great idea!
There was a problem hiding this comment.
Working on a draft for this, will add a comment here when ready.
|
|
||
| Dynamic Instrumentation lets you add metrics, spans, and span tags to running production systems without restarts or code changes, including in third-party libraries. | ||
|
|
||
| Dynamic Instrumentation complements [Live Debugger][23], which captures logs and variable snapshots using the same [expression language][15]. |
There was a problem hiding this comment.
Same comment as on the LD doc - we can duplicate the same copy on both pages if the docs team is okay with it.
What does this PR do? What is the motivation?
We've had a lot of product decisions around live debugger and dynamic instrumentation, but havent formalized them in external docs. Changes in here are mainly around:
Five English documentation pages only. The scrubbing page moves under Live Debugger with redirects from its old URLs. Simulator code and test changes are deferred.
Merge readiness
AI assistance
AI-assisted drafting, implementation checks, and automated validation.
Additional notes