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: articles/machine-learning/v1/how-to-debug-pipelines.md
+2-9Lines changed: 2 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,21 +187,20 @@ Testing scripts locally is a great way to debug major code fragments and complex
187
187
188
188
### Logging options and behavior
189
189
190
-
The following table provides information for different debug options for pipelines. It isn't an exhaustive list, as other options exist besides just the Azure Machine Learning, Python, and OpenCensus ones shown here.
190
+
The following table provides information for different debug options for pipelines. It isn't an exhaustive list, as other options exist besides just the Azure Machine Learningand Python ones shown here.
191
191
192
192
| Library | Type | Example | Destination | Resources |
logger.warning("I am an OpenCensus warning statement, find me in Application Insights!")
227
-
logger.error("I am an OpenCensus error statement with custom dimensions", {'step_id': run.id})
228
224
```
229
225
230
226
## Azure Machine Learning designer
@@ -260,9 +256,6 @@ You can also find the log files for specific runs in the pipeline run detail pag
260
256
> [!IMPORTANT]
261
257
> To update a pipeline from the pipeline run details page, you must **clone** the pipeline run to a new pipeline draft. A pipeline run is a snapshot of the pipeline. It's similar to a log file, and cannot be altered.
262
258
263
-
## Application Insights
264
-
For more information on using the OpenCensus Python library in this manner, see this guide: [Debug and troubleshoot machine learning pipelines in Application Insights](./how-to-log-pipelines-application-insights.md)
265
-
266
259
## Interactive debugging with Visual Studio Code
267
260
268
261
In some cases, you may need to interactively debug the Python code used in your ML pipeline. By using Visual Studio Code (VS Code) and debugpy, you can attach to the code as it runs in the training environment. For more information, visit the [interactive debugging in VS Code guide](how-to-debug-visual-studio-code.md#debug-and-troubleshoot-machine-learning-pipelines).
0 commit comments