> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/audit-and-traceability/application-audit/pipeline.md).

# Pipeline

Click **“Security” →** Click **“Audit Trail” ->** Click **“Pipeline”** and the pipeline screen is shown in the image below: It contains all the pipelines in a list view as shown in the image below:

![](/files/zRLNPqxZ6swmfMstHiN5)

In the above image, the list of pipelines is displayed and has the following details:

·        **Application** – This column shows the application in which the pipeline exists.

·        **Pipeline/Service** – This column shows the name of the pipeline

·        **Modified By** – This column shows the user who modified the pipeline.

### Show/Hide Columns

You can opt to show or hide these columns in the list available. To do so, click the **menu icon** as shown in the image below:

![](/files/Qjh9oJLKQEvzU4FInwuu)

The list of available columns will appear. You can select/deselect a particular column to remove it from the pipeline table. For example – Let us uncheck the Last **Modified By** check box. Now, the pipeline list table will appear without the Last Modified column as shown in the image below:

![](/files/WrP64uv7GphdQqCYszFU)

### Filter Pipelines

Let’s take an example where you have around 200 pipelines in the list. But you want to view the details of one particular pipeline or a set of pipelines. This is where you can apply filter to the list and view the specific pipeline(s) as per your requirement. There are two type of filters available, **Basic** and **Advanced** filters.

#### **Basic Filter**

The basic filter allows you to simply search a pipeline using the name of the pipeline. For example, from the available pipeline list you only want to view the specific pipeline. To do so, enter the name of the pipeline in the **Search** text box and the list will only show the pipeline with that particular name as shown below:

![](/files/lyLnaFeK1ql8P4lYJefD)

#### 
**Filter by Column**

You can also opt to filter the pipelines by the columns of the table showing the list of pipelines. To do so click the filter icon. Refer to the image below:

![](/files/SET15zHljxDttaJAvscU)

As of now, you can only filter by 3 columns. They are as follows:

\
**Application** - Select the check box to filter by the **application** of the pipeline. Once you select a drop down will appear as shown below:

![](/files/bEe5g9jannk2aZ0Uc7AB)

Click the drop-down to select the application for which you want to view. Refer to the above image.

**Pipeline** – Select the check box to filter by the name of the **pipeline**. Once you select a drop down will appear as shown below:

![](/files/MCWh2PDGGzhOgW2qNG00)

Click the drop-down to select the name of the pipeline which you want to view. Refer to the above image.

**Modified By** - Select the check box to filter by the user who modified the pipeline. Once you select a drop down will appear as shown below:

![](/files/oxmYRmDqtuIeIdoLcUXm)

Click the drop-down to select the user. Refer to the above image.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/audit-and-traceability/application-audit/pipeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.