getBlockedVsMonitorTrend
Retrieves trend data showing the ratio of blocked vs monitored pipeline executions over time.
Examples
query GetBlockedVsMonitorTrend($getPipelineSummaryInput: GetPipelineSummaryInput) {
getBlockedVsMonitorTrend(getPipelineSummaryInput: $getPipelineSummaryInput) {
jobTriggeredAt
passed
monitor
block
total
}
}
Variables
This is an example input showing all available input fields. Only fields marked as required in the schema are mandatory.
{
"getPipelineSummaryInput": {
"limit": 100,
"offset": 0,
"owners": ["example"],
"tagIds": ["example"],
"dateRange": {
"from": 1749000000000,
"to": 1749900000000
},
"filters": {
"apps": ["example"],
"result": ["example"],
"jobTriggeredBy": ["example"],
"sourceBranches": ["example"],
"targetBranches": ["example"],
"severities": ["example"],
"eventTypes": ["example"],
"cicdTypes": ["example"],
"tags": ["example"],
"jobId": ["example"],
"scanCompletionStatus": ["example"],
"pipelineScanType": ["example"],
"pipelineArtifactName": ["example"],
"pipelineArtifactTag": ["example"]
},
"openItems": ["digest"]
}
}
Arguments
You can use the following argument(s) to customize your getBlockedVsMonitorTrend
query.
getPipelineSummaryInput GetPipelineSummaryInput
Parameters for filtering which pipeline data to include in the blocked vs monitor trend analysis
limit Int
offset Int
owners [String]
tagIds [String]
dateRange DateRange
filters PipelineSummaryFilters
openItems [FilterTypes]
Fields
Return type: [BlockedVsMonitorTrendRes]
You can use the following field(s) to specify what information your getBlockedVsMonitorTrend
query will return. Please note that some fields may have their own subfields.
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
total Int
Total number of pipeline executions
Last updated