# Verbose debugging in Azure DevOps pipelines

You might already know about the easy button. The diagnostics option is when you manually trigger a pipeline. Are you debugging a pesky pipeline and tired of manually triggering it?

### Background

The diagnostics option is found when queueing a new build.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1637639743591/r6MAOKftQ.png)

Then from the pipeline output, you can see more verbose logs in pretty colors.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1637639745042/myTm2ozNZ.png)

Again, but it can be quite tedious when troubleshooting something intensely.

### Permanently

To do it permanently, you can simply set `system.debug` as a pipeline variable.

    variables:
      System.Debug: true
    

Or you can set it as a separate variable that won’t get source controlled. But it’s probably more effective for secrets really.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1637639746458/q_TmlDaZ2y.png)

If it were me, I would probably forget to remove it.