Monitor and Trigger Continuous Integration Projects

Trigger start/stop actions for specified log reader

Submits an asynchronous lifecycle action (START, STOP) for log reader associated with pipeline within the specified project. A 202 Accepted response indicates the request was validated and dispatched (not that execution is complete). The response body contains a status field (SUBMITTED or FAILED) and the Location header points to the alerts endpoint for monitoring.

Process Overview:

  • Validate caller has replication-pipeline::operate permission.
  • Validate that at least logReader or pipeline is specified in the request.
  • Dispatch start or stop request through the portal client.
  • Build 202 response with body status (SUBMITTED if dispatch succeeded, FAILED if an internal exception occurred) and Location header to alerts.

Key Features:

  • Targeted log reader control (specify logReader and associating pipeline).
  • Uniform 202 response; body-level status differentiates dispatch success vs failure.
  • Immediate monitoring path via Location header (/projects/{projectId}/alerts) for a successfully submitted request.
  • Idempotent friendly: client can safely retry on FAILED since execution had not been confirmed.

Required Permissions: replication-pipeline::operate

post/v1/integration/continuous/monitoring/projects/{projectId}/logreaders/trigger

Request

  • Base URL: https://integration-adapter.connect.cloud.precisely.com
  • URL: https://integration-adapter.connect.cloud.precisely.com/v1/integration/continuous/monitoring/projects/{projectId}/logreaders/trigger
  • Auth: HTTP bearer

Path parameters

projectIdstring required

Unique identifier of the project whose log readers should be acted upon.

Request body

pipelinestring required

Name of the pipeline in which associated log reader has to be triggered.

logReaderstring required

Name of the log reader to trigger.

action'START' | 'STOP' required

Action to perform on the log readers.

Example request

{
  "startOptions": {
    "receiverType": "CURRENT",
    "receiverOffset": 123,
    "sequenceType": "LAST",
    "sequenceOffset": 456
  },
  "action": "START"
}

Response

Accepted. Body status field indicates SUBMITTED or FAILED; If the request is properly submitted, Location header points to alerts endpoint.

messagestring

Informational message describing the outcome of the submission.

status'Submitted' | 'InProgress' | 'Completed' | 'Partial' | 'Failed' | 'Cancelled'

Overall submission status of the trigger request.

Example response

{
  "message": "request START submitted",
  "status": "Submitted"
}

Changes

No recorded changes to this operation across all 1 revision of this API.