curl --request POST \
--url https://developer.synq.io/api/alerts/v1/get \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identifiers": [
{
"fqn": "<string>"
}
]
}
'{
"alerts": {}
}Get multiple alert configurations by their identifiers.
curl --request POST \
--url https://developer.synq.io/api/alerts/v1/get \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identifiers": [
{
"fqn": "<string>"
}
]
}
'{
"alerts": {}
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Success
Alerts mapped by their identifiers.
Show child attributes
Alert represents the configuration for an alert. It contains all the necessary information to trigger and send alerts.
Show child attributes
Query that defines which entities can trigger this alert.
Show child attributes
The parts that compose this entity group query.
1Show child attributes
The logical operand used to combine the query parts (AND, OR, etc.).
QUERY_OPERAND_UNSPECIFIED, QUERY_OPERAND_AND, QUERY_OPERAND_OR, QUERY_OPERAND_EXCEPT, QUERY_OPERAND_UPSTREAM, QUERY_OPERAND_DOWNSTREAM The individual query parts that make up this selection.
1A single part of a selection query.
Show child attributes
Filter by specific entity identifiers.
Show child attributes
Identifier is a unique reference to an entity in SYNQ system. Entity identifiers are designed to closely mimic identifiers used by data platforms and tools. To construct an identifier, you need to know the kind of the entity and the ids that you would normally use to identify it in the data platform or tool. For example, to identify a table in BigQuery, you would need to know the project, dataset, and table names.
Show child attributes
Airflow DAG identifier
Show child attributes
Additional settings for the specific alert type.
Show child attributes
Alert triggered by entity failures (e.g., table failures, test failures).
Show child attributes
Strategy for handling ongoing/repeated alerts.
Show child attributes
Disabled strategy - no ongoing alerts will be sent after the initial alert. No configuration needed - alerts are simply disabled after the first one.
The severity levels that should trigger this alert.
1Severity levels that define the criticality of failures.
SEVERITY_UNSPECIFIED, SEVERITY_WARN, SEVERITY_ERROR, SEVERITY_FATAL Whether to notify upstream dependencies when this alert triggers.
Whether to allow SQL test audit links in alert notifications.
Timestamp when the alert config was created.
Unique identifier for the alert config (system-generated).
1Human-readable name for the alert configuration.
1 - 255User-provided fully qualified name for the alert config. This is a unique identifier that users can specify to reference the alert.
1 - 500List of targets where alerts will be sent.
1AlertingTarget represents a destination where alert notifications will be sent. Each target type has its own specific configuration requirements.
Show child attributes
Owner information for the alert configuration. If set, the alert is attributed to the specified owner and ownership.
Whether the alert config is currently disabled.