Get project alerts - Precisely Data Integrity Suite

Data Integrity Suite APIs
Product
Data_Integrity
Spatial_Analytics
Data_Enrichment
geo_addressing_1
Services
Spatial Analytics
Data Enrichment
Geo Addressing
ft:title
Data Integrity Suite APIs
ft:locale
en-US
PublicationType
pt_developer
copyrightfirst
2023
copyrightlast
2026

Fetches alerts for a specified project, with optional filtering by server name and severity level.

HTML

GET https://hostname/v1/integration/continuous/monitoring/projects/{projectId}/alerts

Process overview

  • Validate permission.
  • Fetch alert stream for project.
  • Apply optional serverName and level filters.
  • Enforce limit bounds (1..5000).

Key features

  • Supports operational triage & dashboards.
  • Level filter aligns with standard logging levels.

Required permissions

replication-pipeline::view

Request

Path parameters

Key Required Type Description
projectId Yes string

Unique identifier of the project.

Query parameters

Key Required Type Description
serverName No string

Filter alerts by runtime server name. If not provided, alerts from all servers will be returned.
level No string

Filter alerts by severity level. If not provided, alerts of all levels will be returned.

limit No integer

Maximum number of alerts to return. Must be a positive integer. Defaults to 500 if not provided.

Response

Response body properties

Property Required Type Description
runtimeServer No string Name of the runtime server where the alert originated.
pipeline No string Name of the pipeline associated with the alert.
level No string Severity level of the alert.
message No string Alert message detailing the issue or information.
generatedAt No string Time indicating when the alert was generated in UTC (RFC3339 format).

Response examples

[
  {
    "runtimeServer": "server-1",
    "pipeline": "my-db2i-to-kafka",
    "level": "INFO",
    "message": "Replication Kernel is shutting down",
    "generatedAt": "2023-10-05T14:48:00Z"
  }
]
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.1",
  "title": "Bad Request",
  "status": 400,
  "detail": "Validation error occurred",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-VAL-0000"
  }
}
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.2",
  "title": "Unauthorized",
  "status": 401,
  "detail": "Authorization failed - missing or invalid credentials",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-AUT-0001"
  }
}
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.4",
  "title": "Forbidden",
  "status": 403,
  "detail": "Authorization failed - insufficient permissions",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-AUT-0002"
  }
}
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.5",
  "title": "Not Found",
  "status": 404,
  "detail": "Not Found - Resource does not exist",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-ALT-0002"
  }
}
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.21",
  "title": "Unprocessable Entity",
  "status": 422,
  "detail": "Unprocessable Entity - Request is syntactically correct but semantically invalid",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-VAL-0001"
  }
}
 
{
  "type": "https://datatracker.ietf.org/doc/html/rfc9110#section-15.6",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "An unexpected error occurred",
  "instance": "/v1/integration/continuous/monitoring/projects/{projectId}/alerts",
  "properties": {
    "errorCode": "DI-ADAPTER-ALT-0001"
  }
}