Operational Insights > Part II: Monitoring Informatica Intelligent Cloud Services > Monitor Informatica Intelligent Cloud Services Application Integration > Export Application Integration job data
  

Export Application Integration job data

You can export Application Integration job execution data from Operational Insights to analyze performance trends, troubleshoot issues, and maintain historical records. Use the GraphQL API to extract job data and integrate it with external reporting and monitoring systems.
To export job data, perform the following steps:
  1. 1Obtain your session ID from the organization from which you want to fetch the data. For more information about session IDs, see Session IDs.
  2. 2Construct a GraphQL query with the required parameters and fields.
  3. 3Submit the query to the Operational Insights GraphQL API endpoint.
  4. 4Receive the response in the CSV format (recommended) or in the JSON format.
Export guidelines
The following guidelines apply to the export functionality:
All exported timestamps use Coordinated Universal Time (UTC).
API endpoint
Use the following API endpoint to export job data:
<Informatica Intelligent Cloud Services URL>/active-bpel/opsanalytics-das/metrics?query={...}
Request header
The following table describes the request headers:
Header
Value
Description
Authorization
Bearer <session_id>
Session ID of the organization.
Content-Type
application/json
Request content type.
Accept
text/csv
Include this header to receive the response in the CSV format. Omit this header to receive the response in the JSON format.

API resources

This topic describes two primary API resources for exporting Application Integration job data.
For the complete GraphQL API schema and additional query options, see the Informatica Knowledge Base article 000259754.
You can configure the GraphQL schema to query and export Application Integration job data in the format that best suits your monitoring and reporting needs.

processJobReport

Use the processJobReport resource to export detailed Application Integration job execution data. You can optionally filter the data by date range, environment, or status.
GET request syntax
To get the details for a specific Application Integration job, send a GET request using the following URI:
<Informatica Intelligent Cloud Services URL>/active-bpel/opsanalytics-das/metrics?query={processJobReport(<optional parameters>)}
Query structure
The processJobReport resource uses the following query parameters:
query {
processJobReport(
start: "<start_date>"
end: "<end_date>"
env: "<environment_name>"
status: "<status_value>"
) {
{
time
processName
endpoint
env:
originContext
status
executionCount
executionTime
averageExecutionTime
}
}
Request parameters
The following table describes the request query parameters:
Parameter
Type
Required
Description
Default value
start
String
Yes
The start date for the export. Use the YYYY-MM-DDTHH:mm:ssZ format. For example: "2024-12-01T00:10:00Z"
Note:
The date range can't exceed 13 months.
None
end
String
Yes
The end date for the export. Use the YYYY-MM-DDTHH:mm:ssZ format. For example: "2024-12-29T09:50:00Z"
Note:
The date range can't exceed 13 months.
None
env
String
No
The runtime environment to filter by. Use a specific environment name or allEnvironments. Includes Secure Agent, Secure Agent group, or Cloud Server.
allEnvironments
status
String
No
The job status to filter by. Use one of the following status value:
  • - Completed
  • - Faulted
allStatuses
Response parameters
The following table describes the response parameters:
Parameter
Type
Description
env
String
The runtime environment in which the job runs.
status
String
The execution status such as, Completed or Faulted.
time
String
The date and time when the job was executed. The time is in UTC format.
processName
String
The name of the Application Integration process.
endpoint
String
The method that triggered the process. Use one of the following methods:
  • - Scheduled. A pre-defined trigger that automatically runs the process at specific intervals or at a set time.
  • - API Trigger. A request that initiates the process using an endpoint.
  • - Manual. An action where you start the process through the Operational Insights interface.
originContext
String
The metadata tracks the source and trigger of an API request.
executionCount
Integer
The number of times that the process ran.
executionTime
Integer
The total execution time in milliseconds.
averageExecutionTime
Integer
The average execution time per run in milliseconds.
The API returns the data in CSV format:
time,processName,endpoint,env,originContext,status,executionCount,executionTime,averageExecutionTime

"<String!>","<String>","<String>","<String>","<String>","<String>",<Int>,<Int>,<Int>
The API returns the data in JSON format if you omit the Accept: text/csv header.
{

"processJobReport": [
{
time: "<String!>"
processName: "<String>"
endpoint: "<String>"
env: "<String>"
originContext: "<String>"
status: "<String>"
executionCount: <Int>
executionTime: <Int>
averageExecutionTime: <Int>
}
]
}
GET request example
You might send a request similar to the following example:
{
"query":{processJobReport(start:"2025-05-01T09:10:00Z",end:"2025-11-06T09:50:00Z"){ time processName env status originContext endpoint executionCount executionTime averageExecutionTime}}
GET response example
You might receive a response similar to the following example:
Include the Accept: text/csv header in your request to receive data in CSV format:
time,processName,endpoint,env,originContext,status,executionCount,executionTime,averageExecutionTime
2026-03-15T10:30:00Z,CustomerDataSync,/api/v1/sync,Production,Scheduled,SUCCESS,45,135000,3000
2026-03-15T11:00:00Z,OrderProcessing,/api/v1/orders,Production,API Trigger,FAILED,2,8500,4250
2026-03-15T12:15:00Z,InventoryUpdate,/api/v1/inventory,Staging,Manual,SUCCESS,12,24000,2000
2026-03-15T13:00:00Z,PaymentProcessor,/api/v1/payments,Production,API Trigger,SUCCESS,78,156000,2000
2026-03-15T14:30:00Z,CustomerDataSync,/api/v1/sync,Production,Scheduled,SUCCESS,42,129000,3071
Omit the Accept: text/csv header to receive data in JSON format:
{
"data": {
"processJobReport": [
{
"time": "2026-03-15T10:30:00Z",
"processName": "CustomerDataSync",
"endpoint": "/api/v1/sync",
"env": "Production",
"originContext": "Scheduled",
"status": "SUCCESS",
"executionCount": 45,
"executionTime": 135000,
"averageExecutionTime": 3000
},
{
"time": "2026-03-15T11:00:00Z",
"processName": "OrderProcessing",
"endpoint": "/api/v1/orders",
"env": "Production",
"originContext": "API Trigger",
"status": "FAILED",
"executionCount": 2,
"executionTime": 8500,
"averageExecutionTime": 4250
}
]
}
}

processRunsByNameEnv

Use the processRunsByNameEnv resource to retrieve aggregated summary statistics for processes grouped by process name and environment. This resource provides a high-level overview of process performance across environments.
GET request syntax
To get the summary statistics for processes by environment, send a GET request using the following URI:
<Informatica Intelligent Cloud Services URL>/active-bpel/opsanalytics-das/metrics?query={processRunsByNameEnv(<optional parameters>)}
Query structure
The processRunsByNameEnv resource uses the following query parameters:
query {
processRunsByNameEnv(
start: "<start_date>"
end: "<end_date>"
env: "<environment_name>"
status: "<status_value>"
) {
processName
env
executionCount
averageExecutionTime
}
}
Request parameters
The following table describes the request query parameters:
Parameter
Type
Required
Description
Default value
start
String
Yes
The start date for the export. Use the YYYY-MM-DD format.
For example: "2026-03-01"
Note:
The date range can't exceed one month.
None
end
String
Yes
The end date for the export. Use the YYYY-MM-DD format.
For example: "2026-03-31"
Note:
The date range can't exceed one month.
None
env
String
No
The runtime environment to filter by. Use a specific environment name or allEnvironments. Includes Secure Agent, Secure Agent group, or Cloud Server.
allEnvironments
status
String
No
The job status to filter by. Use one of the following:
  • - SUCCESS
  • - FAILED
  • - RUNNING
  • - STOPPED
allStatuses
Response parameters
The following table describes the response parameters:
Parameter
Type
Description
processName
String
The name of the process.
env
String
The runtime environment in which the process ran.
executionCount
Integer
The total number of process that runs during the specified date range.
averageExecutionTime
Float
The average execution time in milliseconds.
The API returns the data in CSV format:
processName,env,executionCount,averageExecutionTime

<String>,<String>,<Integer>,<Integer>
The API returns the data in JSON format if you omit the Accept: text/csv header.
{

"processJobReport": [
{
time: "<String!>"
processName: "<String>"
endpoint: "<String>"
env: "<String>"
originContext: "<String>"
status: "<String>"
executionCount: <Int>
executionTime: <Int>
averageExecutionTime: <Int>
}
]
}
GET request example
You might send a request similar to the following example:
{
"query": "query { processRunsByNameEnv(start: "2026-03-01", end: "2026-03-31", env: "Production", status: "_allStatuses_") { processName env executionCount averageExecutionTime } }"
}
GET response example
You might receive a response similar to the following example:
Include the Accept: text/csv header in your request to receive data in CSV format:
processName,env,executionCount,averageExecutionTime
CustomerDataSync,Production,150,2850.5
OrderProcessing,Production,89,4125.3
InventoryUpdate,Production,210,1950.8
PaymentProcessor,Production,456,2100.2
EmailNotification,Production,320,850.4
Omit the Accept: text/csv header to receive data in JSON format:
{
"data": {
"processRunsByNameEnv": [
{
"processName": "CustomerDataSync",
"env": "Production",
"executionCount": 150,
"averageExecutionTime": 2850.5
},
{
"processName": "OrderProcessing",
"env": "Production",
"executionCount": 89,
"averageExecutionTime": 4125.3
}
]
}
}