> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/api-documentation/api-reference/api--pipeline/types/objects/blocked-vs-monitor-trend-res.md).

# blockedVsMonitorTrendRes

Trend data showing blocked vs monitor pipeline results over time.

### Examples

```graphql
type BlockedVsMonitorTrendRes {
  jobTriggeredAt: String
  passed: Int
  monitor: Int
  block: Int
  timeout: Int
  failure: Int
  total: Int
}
```

### Fields

| Field                   | Description                                                                          | Supported fields |
| ----------------------- | ------------------------------------------------------------------------------------ | ---------------- |
| jobTriggeredAt `String` | Timestamp when the pipeline job was triggered                                        |                  |
| passed `Int`            | Number of pipelines that passed security checks                                      |                  |
| monitor `Int`           | Number of pipelines in monitor mode (issues found but not blocking)                  |                  |
| block `Int`             | Number of pipelines blocked due to security issues                                   |                  |
| timeout `Int`           | Number of pipeline scans that exceeded the maximum allowed time and were terminated. |                  |
| failure `Int`           | Number of pipeline scans that failed to complete due to errors.                      |                  |
| total `Int`             | Total number of pipeline executions                                                  |                  |

### References

#### Queries using this object:

* [\<?> getBlockedVsMonitorTrend](/api-documentation/api-reference/api--pipeline/queries/get-blocked-vs-monitor-trend.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/api-documentation/api-reference/api--pipeline/types/objects/blocked-vs-monitor-trend-res.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.