> ## Documentation Index > Fetch the complete documentation index at: https://docs.synq.io/llms.txt > Use this file to discover all available pages before exploring further. # Update > Update an existing alert configuration. The config can be identified by either ID or FQN. ## OpenAPI ````yaml /api-reference/openapi.yaml put /api/alerts/v1 openapi: 3.1.0 info: version: '1.0' title: SYNQ servers: - url: https://developer.synq.io - url: https://api.us.synq.io security: - bearerAuth: [] tags: - name: synq.issues.issues.v1.IssuesService description: IssuesService is a service for managing Issues. - name: synq.issues.v2.IssuesService description: IssuesService is a service for managing Issues. - name: synq.incidents.v1.IncidentsService description: IncidentsService is a service for managing Incidents. - name: synq.alerts.services.v1.AlertsService description: AlertsService provides operations for managing alert configurations. - name: synq.agent.recon.v1.YamlService description: >- YamlService provides stateless conversion between YAML config format and proto. This is useful for UI editors that need to display/edit suite configs as YAML. - name: synq.agent.recon.v1.SuiteDeploymentService description: |- SuiteDeploymentService is the platform plane of reconciliation. SuiteConfigService is the developer/authoring sandbox (edit, version, run ad-hoc with your own credentials — preview-only, no Entity, no Run, no Issue). A deployment is what SYNQ actually runs on the workspace's behalf: a frozen snapshot of a suite config, mapped to workspace-level SYNQ integrations, optionally scheduled or triggerable by API. Identity: every deployment has a stable deployment_id (UUIDv7) assigned on first promote. It survives re-promotes, schedule/mapping changes, and pause/resume. Downstream AssetCommand / RunCommand publication keys off deployment_id so Entity identity does not fragment on promote churn. - name: synq.agent.sre.v1.TriageService description: >- Service for managing issue triage operations, allowing LLM agents to conclude investigations and record evidence during the triage process. - name: synq.agent.sre.v1.LlmService description: Service for evaluating LLM requests and producing structured output. - name: synq.agent.sre.v1.FeatureRequestService description: >- FeatureRequestService allows MCP clients to submit feature requests when users encounter missing capabilities. This is a last-resort service — it should only be used when no existing tool can fulfill the user's request. - name: synq.integrations.v1.IntegrationsService description: |- IntegrationsService manages connections from Coalesce Quality to your data systems (warehouses, databases, and transformation tools). Concurrency: every integration carries an opaque `etag`. Read it from `GetIntegration` / `ListIntegrations`, then pass it back on `UpdateIntegration` / `DeleteIntegration` to ensure you modify the version you last saw. A stale etag is rejected with ABORTED (HTTP 409). Omit the etag for last-write-wins. Quota: each workspace has a limit on the number of integrations. Creating beyond the limit is rejected with RESOURCE_EXHAUSTED. Secrets: credential fields (passwords, tokens, keys) are write-only. They are masked (returned empty) on every read. On update, omit a secret to keep it, send a new value to rotate it, or send an explicit empty string to clear it (where the field is `optional`). - name: synq.auth.iam.v1.IamService - name: synq.monitors.predictions.v1.MonitorPredictionsService description: Access to anomaly detection model predictions and raw metric timeseries. - name: synq.monitors.info.v1.MonitorInfoService - name: synq.monitors.custom_monitors.v1.CustomMonitorsService - name: synq.monitors.history.v1.HistoryService - name: synq.monitors.automated_monitors.v1.DeploymentRulesService - name: synq.entities.executions.v2.EntityExecutionsService description: >- EntityExecutionsService provides read-only access to entity execution history. This service allows customers to retrieve information about all executions that happened on their entities, including execution status, timing, and messages. Use cases: - Retrieve execution history for specific entities - Filter executions by time range, status, or execution type - Get aggregated summaries of execution activity - Track execution trends and patterns - name: synq.datachecks.sqltests.v1.SqlTestsService description: SqlTestsService is a service for managing SqlTests. - name: synq.datachecks.v1.TriggerService description: TriggerService provides synchronous execution of datachecks on entities. - name: synq.datachecks.testsuggestions.v1.TestSuggestionsService - name: synq.extensions.atlan.provider.v1.AtlanProviderService - name: synq.extensions.atlan.integrations.v1.AtlanIntegrationService - name: synq.extensions.atlan.workflows.v1.AtlanWorkflowService - name: synq.platforms.v1.PlatformsService description: PlatformsService is a service for managing Platforms and Integrations. - name: synq.queries.v1.NLQueryService description: >- NLQueryService generates structured Query protos from natural language descriptions using an LLM. - name: synq.schedule.v1.ScheduleService description: ScheduleService provides schedule evaluation utilities. - name: synq.entities.executions.v1.EntityExecutionsService description: 'Deprecated: Use [synq.entities.custom.v1.EntityExecutionsService] instead' - name: synq.entities.status.v1.EntityIncidentsService description: EntityIncidentsService is the service which retrieves entity status. - name: synq.entities.status.v1.EntityIssuesService description: EntityIssuesService is the service which retrieves entity issues status. - name: synq.entities.orchestration.v1.OrchestrationService description: >- OrchestrationService provides information about orchestration relationships between entities. This includes relationships between Airflow tasks and transformation models (dbt, SQLMesh), as well as task-to-task dependencies. - name: synq.entities.coordinates.v1.DatabaseCoordinatesService description: >- DatabaseCoordinatesService is a service for getting database coordinates of Entities. - name: synq.entities.checks.v1.ChecksCategoriesService description: |- ChecksCategoriesService lets workspace admins set explicit category overrides on individual checks. An explicit category is the authoritative category for a check — it takes precedence over the categories computed by the workspace's categorisation rules. It is a public API so customers can manage check categories programmatically; the same service is also mounted on the internal API. The workspace and the acting identity are always taken from the request context, never from the payload. - name: synq.entities.sql_insights.v1.SqlInsightsService description: >- SqlInsightsService exposes analytical information about the SQL used across a workspace's entities. It answers questions such as "which SQL constructs are used in my warehouse, and how often" and "what SQL constructs does this specific entity use", without requiring the caller to re-parse any SQL. - name: synq.entities.custom.v1.RelationshipsService description: >- RelationshipsService allow management of relationships between entities. Relationships can be created, updated, and deleted between 2 custom entities, or between a custom entity and Coalesce Quality native entity.enum There is no option to create relationships between 2 Coalesce Quality native entities (dbt model, BI dashboard, etc.). - name: synq.entities.custom.v1.TypesService description: TypesService is a service for managing custom entity types. - name: synq.entities.custom.v1.GroupsService description: >- It eliminates the need to keep state on client side to remember which assets were already created and which should be deleted. The server will keep track of the current state of the group and client can always send the intended new state. The server will calculate the diff and entities that are no longer present in the group will be removed. Example: 1. group has entities A, B, C at time t1 2. client sends group with entities B, C, D at time t2 3. server will remove entity A from the system and update the current state of the group to B, C, D The service is designed to be idempotent and can be called multiple times with the same state without causing any side effects. - name: synq.entities.custom.v1.EntityExecutionsService - name: synq.entities.custom.v1.EntitiesService description: >- custom.EntitiesService is a service for managing custom entities. Entities can represent various data platform concepts such as services, consumers, applications or data pipelines that are not natively available in Coalesce Quality. Entities are identified by a unique identifier and can be created, updated, read and deleted. - name: synq.entities.custom.v1.FeaturesService - name: synq.entities.impact.v1.ImpactService - name: synq.entities.schemas.v1.SchemaMismatchesService description: >- SchemaMismatchesService provides access to schema drift information between data platform tables and their definitions (e.g., dbt models). - name: synq.entities.schemas.v1.SchemasService description: EntitiesService is a service for retriving any entity. - name: synq.entities.constraints.v1.TableConstraintsService description: >- TableConstraintsService provides access to table constraint and index information. - name: synq.entities.changes.v1.ChangesService description: >- ChangesService provides functionality to track and retrieve all types of changes to data entities. This unified service returns ALL change types for an entity: - Git commits: Changes to code files (dbt models, SQL files) tracked in version control - Schema changes: Database schema modifications (columns added/removed/changed) - SQL definition changes: View/materialized view definition updates detected by Coalesce Quality Changes are returned with structured metadata including: - For git commits: structured statistics (directories, file types, top changes) - For schema changes: detailed column-level diffs - For SQL changes: before/after SQL definitions Use cases: - "What changed in the last week for table X?" → Returns git commits, schema changes, SQL changes - "Show me all commits affecting this dbt model" → Returns git commits with lineage context - "What schema changes happened to this table?" → Returns schema changes detected by Coalesce Quality - name: synq.entities.lineage.v1.LineageService description: |- LineageService allows you to fetch: * Entity level lineage from a starting point of one or more entities. * Column Level lineage from a starting point of multiple columns of a single entity. - name: synq.entities.entities.v1.EntitiesService description: EntitiesService is a service for retriving any entity. - name: synq.entities.annotations.v1.AnnotationsService description: >- AnnotationsService provides operations for managing and querying entity annotations. Annotations are key-value pairs that can be attached to entities for categorization and filtering. - name: synq.entities.code.v1.CodeService description: >- CodeService is a service for retrieving code associated with entities in the system. It provides functionality to access and manage code artifacts such as SQL queries, Python scripts, dbt models, and other code configurations that are part of Coalesce Quality entities. - name: synq.entities.resolve.v1.IdentifierResolveService description: >- IdentifierResolveService resolves identifiers to their Coalesce Quality paths and identities. - name: synq.ingest.airflow.v1.AirflowLogsService - name: synq.ingest.cloudwatch.v1.CloudwatchService - name: synq.ingest.openlineage.v1.OpenlineageService - name: synq.ingest.dwh.v1.DwhService - name: synq.dataproducts.v1.DataproductsService description: DataproductsService can be used to manage data products. - name: synq.git.commits.v1.CommitsService paths: /api/alerts/v1: put: tags: - synq.alerts.services.v1.AlertsService summary: Update description: |- Update an existing alert configuration. The config can be identified by either ID or FQN. operationId: synq.alerts.services.v1.AlertsService.Update requestBody: content: application/json: schema: $ref: '#/components/schemas/synq.alerts.services.v1.UpdateRequest' required: true responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/synq.alerts.services.v1.UpdateResponse' components: schemas: synq.alerts.services.v1.UpdateRequest: type: object properties: identifier: $ref: '#/components/schemas/synq.alerts.services.v1.AlertIdentifier' description: Identifier for the config to update. name: type: string maxLength: 255 minLength: 1 description: Human-readable name for the alert configuration. nullable: true trigger: $ref: '#/components/schemas/synq.alerts.v1.EntityGroupQuery' description: Query that defines which entities can trigger this alert. nullable: true targets: type: array items: $ref: '#/components/schemas/synq.alerts.v1.AlertingTarget' description: |- Targets where alerts will be sent. Leave empty to keep existing targets. settings: $ref: '#/components/schemas/synq.alerts.v1.AlertSettings' description: Additional settings for the specific alert type. nullable: true title: UpdateRequest required: - identifier additionalProperties: false description: > UpdateRequest updates an existing alert configuration. The config can be identified by either ID or FQN. update_request.webhook_incompatible_with_grouped_alerts // Webhook targets are not compatible with grouped alerts. Use the no_grouping strategy when sending alerts to webhook targets. update_request.webhook_incompatible_with_ongoing_alerts // Webhook targets are not compatible with ongoing alert strategies (stream or schedule). Use the disabled ongoing strategy when sending alerts to webhook targets. synq.alerts.services.v1.UpdateResponse: type: object properties: alert: $ref: '#/components/schemas/synq.alerts.v1.Alert' description: The alert configuration that was updated. title: UpdateResponse required: - alert additionalProperties: false description: UpdateResponse returns the updated alert configuration. synq.alerts.services.v1.AlertIdentifier: type: object oneOf: - properties: fqn: type: string title: fqn maxLength: 500 minLength: 1 description: FQN of the alert configuration to update. title: fqn required: - fqn - properties: id: type: string title: id minLength: 1 description: ID of the alert configuration to update. title: id required: - id additionalProperties: false synq.alerts.v1.EntityGroupQuery: type: object properties: parts: type: array items: $ref: '#/components/schemas/synq.alerts.v1.SelectionQuery' minItems: 1 description: The parts that compose this entity group query. title: EntityGroupQuery additionalProperties: false description: |- EntityGroupQuery defines a query to select a group of entities. This is used to specify which entities should be monitored by an alert. synq.alerts.v1.AlertingTarget: type: object oneOf: - properties: email: $ref: '#/components/schemas/synq.alerts.v1.EmailTarget' title: email description: Send alert via email. title: email required: - email - properties: msTeams: $ref: '#/components/schemas/synq.alerts.v1.MsTeamsTarget' title: ms_teams description: Send alert to Microsoft Teams channel or member. title: ms_teams required: - msTeams - properties: owner: $ref: '#/components/schemas/synq.alerts.v1.OwnerTarget' title: owner description: Send alert to the owner of the monitored entity. title: owner required: - owner - properties: slack: $ref: '#/components/schemas/synq.alerts.v1.SlackTarget' title: slack description: Send alert to a Slack channel or user. title: slack required: - slack - properties: webhook: $ref: '#/components/schemas/synq.alerts.v1.WebhookTarget' title: webhook description: Send alert via webhook integration. title: webhook required: - webhook additionalProperties: false description: >- AlertingTarget represents a destination where alert notifications will be sent. Each target type has its own specific configuration requirements. synq.alerts.v1.AlertSettings: type: object oneOf: - properties: issue: $ref: '#/components/schemas/synq.alerts.v1.IssueAlertSettings' title: issue description: >- Unified issue alert settings (replaces entity_failure and issue_lifecycle). title: issue required: - issue - properties: schemaChange: $ref: '#/components/schemas/synq.alerts.v1.SchemaChangeAlertSettings' title: schema_change description: Alert triggered by schema changes. title: schema_change required: - schemaChange additionalProperties: false description: >- AlertSettings defines the properties that affect the trigger and presentation of an alert. It specifies the conditions under which an alert should be fired and how it should behave. synq.alerts.v1.Alert: type: object properties: id: type: string minLength: 1 description: Unique identifier for the alert config (system-generated). name: type: string maxLength: 255 minLength: 1 description: Human-readable name for the alert configuration. fqn: type: string maxLength: 500 minLength: 1 description: |- User-provided fully qualified name for the alert config. This is a unique identifier that users can specify to reference the alert. nullable: true trigger: $ref: '#/components/schemas/synq.alerts.v1.EntityGroupQuery' description: Query that defines which entities can trigger this alert. targets: type: array items: $ref: '#/components/schemas/synq.alerts.v1.AlertingTarget' minItems: 1 description: List of targets where alerts will be sent. settings: $ref: '#/components/schemas/synq.alerts.v1.AlertSettings' description: Additional settings for the specific alert type. owner: $ref: '#/components/schemas/synq.alerts.v1.Alert.Owner' nullable: true createdAt: $ref: '#/components/schemas/google.protobuf.Timestamp' description: Timestamp when the alert config was created. isDisabled: type: boolean description: Whether the alert config is currently disabled. title: Alert required: - trigger - settings - createdAt additionalProperties: false description: |- Alert represents the configuration for an alert. It contains all the necessary information to trigger and send alerts. synq.alerts.v1.SelectionQuery: type: object properties: parts: type: array items: $ref: '#/components/schemas/synq.alerts.v1.SelectionQuery.QueryPart' minItems: 1 description: The individual query parts that make up this selection. operand: $ref: '#/components/schemas/synq.queries.v1.QueryOperand' description: The logical operand used to combine the query parts (AND, OR, etc.). title: SelectionQuery required: - operand additionalProperties: false description: > SelectionQuery represents a query that selects entities based on various criteria. It combines multiple query parts with a logical operand. selection_query.except_requires_two_parts // QUERY_OPERAND_EXCEPT requires exactly 2 parts synq.alerts.v1.EmailTarget: type: object properties: recipientEmails: type: array items: type: string format: email minItems: 1 minItems: 1 description: |- List of email addresses that will receive the alert notifications. Each email must be a valid email address format. title: EmailTarget additionalProperties: false description: EmailTarget configures alert delivery via email. synq.alerts.v1.MsTeamsTarget: type: object properties: channel: type: string minLength: 1 description: Teams channel name or ID. title: MsTeamsTarget additionalProperties: false description: |- MsTeamsTarget configures alert delivery to Microsoft Teams. Alerts are sent to a Microsoft Teams channel. synq.alerts.v1.OwnerTarget: type: object properties: ownerPath: type: string minLength: 1 description: |- Path that identifies the ownership context for this target. This determines how the system will resolve the actual owner. title: OwnerTarget additionalProperties: false description: >- OwnerTarget configures alert delivery to the owner of the monitored entity. This allows alerts to be automatically sent to whoever owns the data being monitored. synq.alerts.v1.SlackTarget: type: object properties: channel: type: string minLength: 1 description: Slack channel name or ID (e.g., "#alerts" or "C1234567890"). title: SlackTarget additionalProperties: false description: |- SlackTarget configures alert delivery to Slack. Alerts are sent to a Slack channel. synq.alerts.v1.WebhookTarget: type: object properties: webhookId: type: string minLength: 1 description: |- Unique identifier of the webhook to send alerts to. This references a pre-configured webhook in the system. title: WebhookTarget additionalProperties: false description: |- WebhookTarget configures alert delivery via webhook/hook integrations. This allows integration with external systems and custom notification workflows. synq.alerts.v1.IssueAlertSettings: type: object properties: severities: type: array items: $ref: '#/components/schemas/synq.v1.Severity' minItems: 1 description: The severity levels that should trigger this alert. notifyUpstream: type: boolean description: Whether to notify upstream dependencies when this alert triggers. allowSqlTestAuditLink: type: boolean description: Whether to allow SQL test audit links in alert notifications. ongoing: $ref: '#/components/schemas/synq.alerts.v1.OngoingAlertsStrategy' description: Strategy for handling ongoing/repeated alerts. grouping: $ref: '#/components/schemas/synq.alerts.v1.IssueGroupingStrategy' description: Strategy for grouping issues in alert notifications. title: IssueAlertSettings required: - ongoing additionalProperties: false description: >- IssueAlertSettings is the unified alert settings type for issue-based alerts. It replaces both EntityFailureAlertSettings and IssueLifecycleAlertSettings. synq.alerts.v1.SchemaChangeAlertSettings: type: object properties: notifyUpstream: type: boolean description: Whether to notify upstream dependencies when schema changes occur. title: SchemaChangeAlertSettings additionalProperties: false description: |- SchemaChangeAlertSettings configures alerts for schema changes. This alert triggers when the schema of monitored entities changes. synq.alerts.v1.Alert.Owner: type: object properties: ownerPath: type: string minLength: 1 description: Path identifying the owner of this alert config. ownershipId: type: string minLength: 1 description: Ownership identifier. title: Owner additionalProperties: false description: |- Owner information for the alert configuration. If set, the alert is attributed to the specified owner and ownership. google.protobuf.Timestamp: type: string examples: - '2023-01-15T01:30:15.01Z' - '2024-12-25T12:00:00Z' format: date-time description: >- A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format. synq.alerts.v1.SelectionQuery.QueryPart: type: object oneOf: - properties: identifierList: $ref: '#/components/schemas/synq.queries.v1.IdentifierList' title: identifier_list description: Filter by specific entity identifiers. title: identifier_list required: - identifierList - properties: inDataPlatform: $ref: '#/components/schemas/synq.queries.v1.InDataPlatform' title: in_data_platform description: Filter by data platform. title: in_data_platform required: - inDataPlatform - properties: inDataproduct: $ref: '#/components/schemas/synq.queries.v1.InDataproduct' title: in_dataproduct description: Filter by data product membership. title: in_dataproduct required: - inDataproduct - properties: inFolder: $ref: '#/components/schemas/synq.queries.v1.InFolder' title: in_folder description: Filter by folder location. title: in_folder required: - inFolder - properties: query: $ref: '#/components/schemas/synq.alerts.v1.SelectionQuery' title: query description: Nested selection query for complex filtering. title: query required: - query - properties: unsupported: $ref: '#/components/schemas/synq.queries.v1.Unsupported' title: unsupported description: Unsupported query types for backward compatibility. title: unsupported required: - unsupported - properties: withAnnotation: $ref: '#/components/schemas/synq.queries.v1.WithAnnotation' title: with_annotation description: Filter by annotation presence/value. title: with_annotation required: - withAnnotation - properties: withDataPlatformType: $ref: '#/components/schemas/synq.queries.v1.WithDataPlatformType' title: with_data_platform_type description: Filter by data platform type. title: with_data_platform_type required: - withDataPlatformType - properties: withNameSearch: $ref: '#/components/schemas/synq.queries.v1.WithNameSearch' title: with_name_search description: Filter by name pattern search. title: with_name_search required: - withNameSearch - properties: withType: $ref: '#/components/schemas/synq.queries.v1.WithType' title: with_type description: Filter by entity type. title: with_type required: - withType additionalProperties: false description: A single part of a selection query. synq.queries.v1.QueryOperand: type: string title: QueryOperand enum: - QUERY_OPERAND_UNSPECIFIED - QUERY_OPERAND_AND - QUERY_OPERAND_OR - QUERY_OPERAND_EXCEPT - QUERY_OPERAND_UPSTREAM - QUERY_OPERAND_DOWNSTREAM description: >- QueryOperand defines how multiple QueryParts within a Query are combined. synq.v1.Severity: type: string title: Severity enum: - SEVERITY_UNSPECIFIED - SEVERITY_WARN - SEVERITY_ERROR - SEVERITY_FATAL synq.alerts.v1.OngoingAlertsStrategy: type: object oneOf: - properties: disabled: $ref: >- #/components/schemas/synq.alerts.v1.OngoingAlertsStrategy.Disabled title: disabled title: disabled required: - disabled - properties: schedule: $ref: >- #/components/schemas/synq.alerts.v1.OngoingAlertsStrategy.Schedule title: schedule title: schedule required: - schedule - properties: stream: $ref: '#/components/schemas/synq.alerts.v1.OngoingAlertsStrategy.Stream' title: stream title: stream required: - stream additionalProperties: false description: |- OngoingAlertsStrategy defines how to handle ongoing/repeated alerts. This prevents alert spam by controlling notification frequency. synq.alerts.v1.IssueGroupingStrategy: type: object oneOf: - properties: noGrouping: $ref: >- #/components/schemas/synq.alerts.v1.IssueGroupingStrategy.NoGrouping title: no_grouping title: no_grouping required: - noGrouping - properties: systemDetected: $ref: >- #/components/schemas/synq.alerts.v1.IssueGroupingStrategy.SystemDetected title: system_detected title: system_detected required: - systemDetected additionalProperties: false description: >- IssueGroupingStrategy controls how issues are grouped for alerting purposes. synq.queries.v1.IdentifierList: type: object properties: identifiers: type: array items: $ref: '#/components/schemas/synq.entities.v1.Identifier' title: IdentifierList additionalProperties: false description: Resolves to entities matching any of the given identifiers. synq.queries.v1.InDataPlatform: type: object properties: identifier: $ref: '#/components/schemas/synq.platforms.v1.DataPlatformIdentifier' title: InDataPlatform additionalProperties: false description: Resolves to all entities that belong to the given data platform. synq.queries.v1.InDataproduct: type: object properties: identifier: $ref: '#/components/schemas/synq.entities.v1.DataproductIdentifier' title: InDataproduct additionalProperties: false description: Resolves to all the assets that belong to the given data product. synq.queries.v1.InFolder: type: object properties: path: type: array items: type: string title: InFolder additionalProperties: false description: Resolves to all entities belonging to the given folder structure. synq.queries.v1.Unsupported: type: object properties: queryJson: type: string title: Unsupported additionalProperties: false description: >- Collects all the parts of the query that are currently unsupported in translation. These represent an internal structure that are not yet completely available on the API. synq.queries.v1.WithAnnotation: type: object properties: name: type: string acceptedValue: type: string nullable: true deprecated: true acceptedValues: type: array items: type: string title: WithAnnotation additionalProperties: false description: >- Resolves to all entities that contain the annotation with at least one of the provided accepted values. In case of no given accepted values, all entities that carry the given annotation are returned. synq.queries.v1.WithDataPlatformType: type: object properties: types: type: array items: $ref: '#/components/schemas/synq.platforms.v1.DataPlatformType' title: WithDataPlatformType additionalProperties: false synq.queries.v1.WithNameSearch: type: object properties: searchQuery: type: string title: WithNameSearch additionalProperties: false description: Resolves to all entities matching the given name search. synq.queries.v1.WithType: type: object properties: type: $ref: '#/components/schemas/synq.queries.v1.WithType.Type' deprecated: true types: type: array items: $ref: '#/components/schemas/synq.queries.v1.WithType.Type' title: WithType additionalProperties: false description: Resolves to all the entities that have the provided type. synq.alerts.v1.OngoingAlertsStrategy.Disabled: type: object title: Disabled additionalProperties: false description: >- Disabled strategy - no ongoing alerts will be sent after the initial alert. No configuration needed - alerts are simply disabled after the first one. synq.alerts.v1.OngoingAlertsStrategy.Schedule: type: object properties: cron: type: string minLength: 1 description: |- Cron expression defining when ongoing alerts should be sent. Must be a valid cron expression (e.g., "0 9 * * MON" for every Monday at 9 AM). title: Schedule additionalProperties: false description: Schedule strategy - alerts are sent on a scheduled basis. synq.alerts.v1.OngoingAlertsStrategy.Stream: type: object title: Stream additionalProperties: false description: >- Stream strategy - alerts are sent continuously as issues persist. No configuration needed - alerts stream continuously. synq.alerts.v1.IssueGroupingStrategy.NoGrouping: type: object title: NoGrouping additionalProperties: false description: NoGrouping - each issue triggers a separate alert. synq.alerts.v1.IssueGroupingStrategy.SystemDetected: type: object title: SystemDetected additionalProperties: false description: SystemDetected - the system automatically groups related issues. synq.entities.v1.Identifier: type: object oneOf: - properties: airflowDag: $ref: '#/components/schemas/synq.entities.v1.AirflowDagIdentifier' title: airflow_dag description: Airflow DAG identifier title: airflow_dag required: - airflowDag - properties: airflowTask: $ref: '#/components/schemas/synq.entities.v1.AirflowTaskIdentifier' title: airflow_task description: Airflow task identifier within a given DAG title: airflow_task required: - airflowTask - properties: athenaTable: $ref: '#/components/schemas/synq.entities.v1.AthenaTableIdentifier' title: athena_table description: Amazon Athena (Glue) table identifier title: athena_table required: - athenaTable - properties: bigqueryTable: $ref: '#/components/schemas/synq.entities.v1.BigqueryTableIdentifier' title: bigquery_table description: BigQuery table identifier title: bigquery_table required: - bigqueryTable - properties: clickhouseTable: $ref: '#/components/schemas/synq.entities.v1.ClickhouseTableIdentifier' title: clickhouse_table description: Clickhouse table identifier title: clickhouse_table required: - clickhouseTable - properties: custom: $ref: '#/components/schemas/synq.entities.v1.CustomIdentifier' title: custom description: Custom identifier to be used with all custom created entities title: custom required: - custom - properties: databricksTable: $ref: '#/components/schemas/synq.entities.v1.DatabricksTableIdentifier' title: databricks_table description: Databricks table identifier title: databricks_table required: - databricksTable - properties: dataproduct: $ref: '#/components/schemas/synq.entities.v1.DataproductIdentifier' title: dataproduct description: Dataproduct identifier title: dataproduct required: - dataproduct - properties: dbtCloudNode: $ref: '#/components/schemas/synq.entities.v1.DbtCloudNodeIdentifier' title: dbt_cloud_node description: >- Dbt node that identifies one of dbt DAG nodes (model, test, etc) in dbt Cloud project title: dbt_cloud_node required: - dbtCloudNode - properties: dbtCoreNode: $ref: '#/components/schemas/synq.entities.v1.DbtCoreNodeIdentifier' title: dbt_core_node description: >- Dbt node that identifies one of dbt DAG nodes (model, test, etc) in dbt Core project title: dbt_core_node required: - dbtCoreNode - properties: monitor: $ref: '#/components/schemas/synq.entities.v1.MonitorIdentifier' title: monitor description: Monitor identifier title: monitor required: - monitor - properties: mssqlTable: $ref: '#/components/schemas/synq.entities.v1.MssqlTableIdentifier' title: mssql_table description: SQL Server table identifier title: mssql_table required: - mssqlTable - properties: mysqlTable: $ref: '#/components/schemas/synq.entities.v1.MysqlTableIdentifier' title: mysql_table description: Mysql table identifier title: mysql_table required: - mysqlTable - properties: oracleTable: $ref: '#/components/schemas/synq.entities.v1.OracleTableIdentifier' title: oracle_table description: Oracle table identifier title: oracle_table required: - oracleTable - properties: postgresTable: $ref: '#/components/schemas/synq.entities.v1.PostgresTableIdentifier' title: postgres_table description: Postgres table identifier title: postgres_table required: - postgresTable - properties: redshiftTable: $ref: '#/components/schemas/synq.entities.v1.RedshiftTableIdentifier' title: redshift_table description: Redshift table identifier title: redshift_table required: - redshiftTable - properties: snowflakeTable: $ref: '#/components/schemas/synq.entities.v1.SnowflakeTableIdentifier' title: snowflake_table description: Snowflake table identifier title: snowflake_table required: - snowflakeTable - properties: sqlMeshAudit: $ref: '#/components/schemas/synq.entities.v1.SqlMeshAuditIdentifier' title: sql_mesh_audit description: SQLMesh Audit identifier title: sql_mesh_audit required: - sqlMeshAudit - properties: sqlMeshModel: $ref: '#/components/schemas/synq.entities.v1.SqlMeshModelIdentifier' title: sql_mesh_model description: SQLMesh Model identifier title: sql_mesh_model required: - sqlMeshModel - properties: synqPath: $ref: '#/components/schemas/synq.entities.v1.SynqPathIdentifier' title: synq_path description: SynqPath identifier title: synq_path required: - synqPath - properties: trinoTable: $ref: '#/components/schemas/synq.entities.v1.TrinoTableIdentifier' title: trino_table description: Trino table identifier title: trino_table required: - trinoTable additionalProperties: false description: >- Identifier is a unique reference to an entity in Coalesce Quality 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. synq.platforms.v1.DataPlatformIdentifier: type: object oneOf: - properties: athena: $ref: '#/components/schemas/synq.platforms.v1.AthenaIdentifier' title: athena title: athena required: - athena - properties: bigquery: $ref: '#/components/schemas/synq.platforms.v1.BigqueryIdentifier' title: bigquery title: bigquery required: - bigquery - properties: clickhouse: $ref: '#/components/schemas/synq.platforms.v1.ClickhouseIdentifier' title: clickhouse title: clickhouse required: - clickhouse - properties: databricks: $ref: '#/components/schemas/synq.platforms.v1.DatabricksIdentifier' title: databricks title: databricks required: - databricks - properties: dbtCloud: $ref: '#/components/schemas/synq.platforms.v1.DbtCloudIdentifier' title: dbt_cloud title: dbt_cloud required: - dbtCloud - properties: duckdb: $ref: '#/components/schemas/synq.platforms.v1.DuckDbIdentifier' title: duckdb title: duckdb required: - duckdb - properties: mssql: $ref: '#/components/schemas/synq.platforms.v1.MssqlIdentifier' title: mssql title: mssql required: - mssql - properties: mysql: $ref: '#/components/schemas/synq.platforms.v1.MysqlIdentifier' title: mysql title: mysql required: - mysql - properties: oracle: $ref: '#/components/schemas/synq.platforms.v1.OracleIdentifier' title: oracle title: oracle required: - oracle - properties: postgres: $ref: '#/components/schemas/synq.platforms.v1.PostgresIdentifier' title: postgres title: postgres required: - postgres - properties: redshift: $ref: '#/components/schemas/synq.platforms.v1.RedshiftIdentifier' title: redshift title: redshift required: - redshift - properties: snowflake: $ref: '#/components/schemas/synq.platforms.v1.SnowflakeIdentifier' title: snowflake title: snowflake required: - snowflake - properties: sqlMesh: $ref: '#/components/schemas/synq.platforms.v1.SqlMeshIdentifier' title: sql_mesh title: sql_mesh required: - sqlMesh - properties: synqIntegrationId: type: string title: synq_integration_id description: >- Coalesce Quality integration ID maps to the created integration on the Coalesce Quality platform. title: synq_integration_id required: - synqIntegrationId - properties: trino: $ref: '#/components/schemas/synq.platforms.v1.TrinoIdentifier' title: trino title: trino required: - trino - properties: unknown: $ref: '#/components/schemas/synq.platforms.v1.UnknownDataPlatform' title: unknown title: unknown required: - unknown additionalProperties: false description: >- DataPlatformIdentifier is a unique reference to a data platform integrated with Coalesce Quality. synq.entities.v1.DataproductIdentifier: type: object properties: id: type: string format: uuid description: Dataproduct id that identifies the Dataproduct title: DataproductIdentifier required: - id additionalProperties: false synq.platforms.v1.DataPlatformType: type: string title: DataPlatformType enum: - DATA_PLATFORM_TYPE_UNSPECIFIED - DATA_PLATFORM_TYPE_BIGQUERY - DATA_PLATFORM_TYPE_LOOKER - DATA_PLATFORM_TYPE_DBT - DATA_PLATFORM_TYPE_DBT_CLOUD - DATA_PLATFORM_TYPE_DBT_SELF_HOSTED - DATA_PLATFORM_TYPE_SNOWFLAKE - DATA_PLATFORM_TYPE_GCP - DATA_PLATFORM_TYPE_GIT - DATA_PLATFORM_TYPE_GITHUB - DATA_PLATFORM_TYPE_REDSHIFT - DATA_PLATFORM_TYPE_TABLEAU - DATA_PLATFORM_TYPE_AIRFLOW - DATA_PLATFORM_TYPE_CLICKHOUSE - DATA_PLATFORM_TYPE_POSTGRES - DATA_PLATFORM_TYPE_MYSQL - DATA_PLATFORM_TYPE_DATABRICKS - DATA_PLATFORM_TYPE_SQLMESH - DATA_PLATFORM_TYPE_DUCKDB - DATA_PLATFORM_TYPE_TRINO - DATA_PLATFORM_TYPE_ATLAN - DATA_PLATFORM_TYPE_COALESCE - DATA_PLATFORM_TYPE_CASTORDOC - DATA_PLATFORM_TYPE_POWERBI - DATA_PLATFORM_TYPE_THOUGHTSPOT - DATA_PLATFORM_TYPE_SIGMA - DATA_PLATFORM_TYPE_DOMO - DATA_PLATFORM_TYPE_MSSQL - DATA_PLATFORM_TYPE_ORACLE - DATA_PLATFORM_TYPE_ATHENA - DATA_PLATFORM_TYPE_SYNQ synq.queries.v1.WithType.Type: type: object oneOf: - properties: custom: type: integer title: custom format: int32 description: >- Custom types as defined through synq.entities.custom.v1.TypesService title: custom required: - custom - properties: default: $ref: '#/components/schemas/synq.entities.v1.EntityType' title: default description: Default Coalesce Quality types title: default required: - default additionalProperties: false synq.entities.v1.AirflowDagIdentifier: type: object properties: integrationId: type: string description: Coalesce Quality integration_id that identifies the Airflow instance dagId: type: string description: Airflow dag_id that identifies the DAG title: AirflowDagIdentifier required: - integrationId - dagId additionalProperties: false synq.entities.v1.AirflowTaskIdentifier: type: object properties: integrationId: type: string description: Coalesce Quality integration_id that identifies the Airflow instance dagId: type: string description: Airflow dag_id that identifies the DAG taskId: type: string description: Airflow task_id that identifies the task within the DAG title: AirflowTaskIdentifier required: - integrationId - dagId - taskId additionalProperties: false synq.entities.v1.AthenaTableIdentifier: type: object properties: instance: type: string description: |- AWS account and region the Athena workgroup runs in, formatted as "." (e.g. "123456789012.eu-west-1"). Auto-derived from sts:GetCallerIdentity at integration setup time. catalog: type: string description: |- Glue Data Catalog name. Almost always "AwsDataCatalog" — the default catalog for Athena unless the customer registered a federated catalog. database: type: string description: Glue database (the namespace users typically filter on). table: type: string description: Glue table or view name. title: AthenaTableIdentifier required: - instance - catalog - database - table additionalProperties: false synq.entities.v1.BigqueryTableIdentifier: type: object properties: project: type: string description: BigQuery project dataset: type: string description: BigQuery dataset id table: type: string description: BigQuery table name title: BigqueryTableIdentifier required: - project - dataset - table additionalProperties: false synq.entities.v1.ClickhouseTableIdentifier: type: object properties: host: type: string description: Clickhouse hostname without port schema: type: string description: Clickhouse database table: type: string description: Clickhouse table title: ClickhouseTableIdentifier required: - host - schema - table additionalProperties: false synq.entities.v1.CustomIdentifier: type: object properties: id: type: string description: |- Id that identifies the custom entity The Id should be unique within the custom entity Identifier. title: CustomIdentifier required: - id additionalProperties: false synq.entities.v1.DatabricksTableIdentifier: type: object properties: workspace: type: string description: URL of Databricks workspace catalog: type: string description: Databricks catalog schema: type: string description: Databricks schema table: type: string description: Databricks table or view title: DatabricksTableIdentifier required: - workspace - catalog - schema - table additionalProperties: false synq.entities.v1.DbtCloudNodeIdentifier: type: object properties: projectId: type: string description: Your dbt Cloud project id accountId: type: string description: Your dbt Cloud account id nodeId: type: string description: Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) title: DbtCloudNodeIdentifier required: - projectId - nodeId additionalProperties: false synq.entities.v1.DbtCoreNodeIdentifier: type: object properties: integrationId: type: string format: uuid description: Coalesce Quality integration_id that identifies the dbt Core project nodeId: type: string description: Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) title: DbtCoreNodeIdentifier required: - integrationId - nodeId additionalProperties: false synq.entities.v1.MonitorIdentifier: type: object properties: monitoredId: $ref: '#/components/schemas/synq.entities.v1.Identifier' description: Identifier of the monitored entity monitorId: type: string description: Identifier of the monitor segment: type: string description: Optional monitor segmentation identifier nullable: true integrationId: type: string description: Coalesce Quality integration_id of the monitored identifier nullable: true deprecated: true title: MonitorIdentifier required: - monitoredId - monitorId additionalProperties: false synq.entities.v1.MssqlTableIdentifier: type: object properties: host: type: string description: Hostname of the SQL Server instance database: type: string description: SQL Server database schema: type: string description: SQL Server schema (e.g. "dbo") table: type: string description: SQL Server table or view title: MssqlTableIdentifier required: - host - database - schema - table additionalProperties: false synq.entities.v1.MysqlTableIdentifier: type: object properties: host: type: string description: Mysql hostname without port schema: type: string description: Mysql database table: type: string description: Mysql table title: MysqlTableIdentifier required: - host - schema - table additionalProperties: false synq.entities.v1.OracleTableIdentifier: type: object properties: host: type: string description: Hostname of the Oracle instance serviceName: type: string description: Oracle service name (PDB) schema: type: string description: Oracle schema (= owning user) table: type: string description: Oracle table or view title: OracleTableIdentifier required: - host - serviceName - schema - table additionalProperties: false synq.entities.v1.PostgresTableIdentifier: type: object properties: host: type: string description: Postgres hostname without port database: type: string description: Postgres database schema: type: string description: Postgres schema table: type: string description: Postgres table title: PostgresTableIdentifier required: - host - database - schema - table additionalProperties: false synq.entities.v1.RedshiftTableIdentifier: type: object properties: cluster: type: string description: Redshift cluster database: type: string description: Redshift database schema: type: string description: Redshift schema table: type: string description: Redshift table title: RedshiftTableIdentifier required: - database - schema - table additionalProperties: false synq.entities.v1.SnowflakeTableIdentifier: type: object properties: account: type: string description: Snowflake account database: type: string description: Snowflake database schema: type: string description: Snowflake schema table: type: string description: Snowflake table title: SnowflakeTableIdentifier required: - account - database - schema - table additionalProperties: false synq.entities.v1.SqlMeshAuditIdentifier: type: object properties: integrationId: type: string format: uuid description: Coalesce Quality integration_id that identifies the dbt Core project fqn: type: string description: SQLMesh model fully qualified name auditId: type: string description: Identifier of the audit title: SqlMeshAuditIdentifier required: - integrationId - fqn - auditId additionalProperties: false synq.entities.v1.SqlMeshModelIdentifier: type: object properties: integrationId: type: string format: uuid description: Coalesce Quality integration_id that identifies the dbt Core project fqn: type: string description: SQLMesh model fully qualified name title: SqlMeshModelIdentifier required: - integrationId - fqn additionalProperties: false synq.entities.v1.SynqPathIdentifier: type: object properties: path: type: string description: >- Coalesce Quality path that identifies the Coalesce Quality entity, needs to be one of supported paths title: SynqPathIdentifier required: - path additionalProperties: false synq.entities.v1.TrinoTableIdentifier: type: object properties: host: type: string description: Hostname of the Trino instance catalog: type: string description: Trino catalog schema: type: string description: Trino schema table: type: string description: Trino table or view title: TrinoTableIdentifier required: - host - catalog - schema - table additionalProperties: false synq.platforms.v1.AthenaIdentifier: type: object properties: instance: type: string description: |- AWS account and region the Athena workgroup runs in, formatted as "." (e.g. "123456789012.eu-west-1"). Auto-derived by SYNQ from sts:GetCallerIdentity at integration setup time. catalog: type: string description: |- Glue Data Catalog name. Almost always "AwsDataCatalog" — the default catalog for Athena unless the customer registered a federated catalog. title: AthenaIdentifier required: - instance - catalog additionalProperties: false synq.platforms.v1.BigqueryIdentifier: type: object properties: project: type: string description: BigQuery project title: BigqueryIdentifier required: - project additionalProperties: false synq.platforms.v1.ClickhouseIdentifier: type: object properties: host: type: string description: Clickhouse host inclusive of port schema: type: string description: Clickhouse database title: ClickhouseIdentifier required: - host - schema additionalProperties: false synq.platforms.v1.DatabricksIdentifier: type: object properties: workspace: type: string description: URL of the databricks workspace title: DatabricksIdentifier required: - workspace additionalProperties: false synq.platforms.v1.DbtCloudIdentifier: type: object properties: apiEndpoint: type: string description: API endpoint for Dbt Cloud accountId: type: string description: Account ID projectId: type: string description: Project ID title: DbtCloudIdentifier required: - apiEndpoint - accountId - projectId additionalProperties: false synq.platforms.v1.DuckDbIdentifier: type: object properties: motherduckAccount: type: string title: DuckDbIdentifier additionalProperties: false synq.platforms.v1.MssqlIdentifier: type: object properties: host: type: string description: SQL Server host database: type: string description: Database name title: MssqlIdentifier required: - host - database additionalProperties: false synq.platforms.v1.MysqlIdentifier: type: object properties: host: type: string description: Mysql host inclusive of port title: MysqlIdentifier required: - host additionalProperties: false synq.platforms.v1.OracleIdentifier: type: object properties: host: type: string description: Oracle host serviceName: type: string description: Oracle service name (PDB) title: OracleIdentifier required: - host - serviceName additionalProperties: false synq.platforms.v1.PostgresIdentifier: type: object properties: host: type: string description: Postgres host inclusive of port database: type: string description: Postgres database title: PostgresIdentifier required: - host - database additionalProperties: false synq.platforms.v1.RedshiftIdentifier: type: object properties: cluster: type: string description: Redshift cluster database: type: string description: Redshift database title: RedshiftIdentifier required: - cluster - database additionalProperties: false synq.platforms.v1.SnowflakeIdentifier: type: object properties: account: type: string description: Snowflake account database: type: string description: Snowflake database title: SnowflakeIdentifier required: - account - database additionalProperties: false synq.platforms.v1.SqlMeshIdentifier: type: object properties: defaultDatabaseInstance: type: string description: Default database instance for SQL Mesh title: SqlMeshIdentifier required: - defaultDatabaseInstance additionalProperties: false synq.platforms.v1.TrinoIdentifier: type: object properties: coordinator: type: string title: TrinoIdentifier additionalProperties: false synq.platforms.v1.UnknownDataPlatform: type: object title: UnknownDataPlatform additionalProperties: false synq.entities.v1.EntityType: type: string title: EntityType enum: - ENTITY_TYPE_UNSPECIFIED - ENTITY_TYPE_BQ_TABLE - ENTITY_TYPE_BQ_VIEW - ENTITY_TYPE_LOOKER_LOOK - ENTITY_TYPE_LOOKER_EXPLORE - ENTITY_TYPE_LOOKER_VIEW - ENTITY_TYPE_LOOKER_DASHBOARD - ENTITY_TYPE_DBT_MODEL - ENTITY_TYPE_DBT_TEST - ENTITY_TYPE_DBT_SOURCE - ENTITY_TYPE_DBT_PROJECT - ENTITY_TYPE_DBT_METRIC - ENTITY_TYPE_DBT_SNAPSHOT - ENTITY_TYPE_DBT_SEED - ENTITY_TYPE_DBT_ANALYSIS - ENTITY_TYPE_DBT_EXPOSURE - ENTITY_TYPE_DBT_GROUP - ENTITY_TYPE_DBT_SEMANTIC_MODEL - ENTITY_TYPE_DBT_CLOUD_PROJECT - ENTITY_TYPE_DBT_CLOUD_JOB - ENTITY_TYPE_SNOWFLAKE_TABLE - ENTITY_TYPE_SNOWFLAKE_VIEW - ENTITY_TYPE_SNOWFLAKE_STREAM - ENTITY_TYPE_SNOWFLAKE_DYNAMIC_TABLE - ENTITY_TYPE_SNOWFLAKE_TASK - ENTITY_TYPE_SNOWFLAKE_EXTERNAL_TABLE - ENTITY_TYPE_SNOWFLAKE_MATERIALIZED_VIEW - ENTITY_TYPE_SNOWFLAKE_PROCEDURE - ENTITY_TYPE_SNOWFLAKE_FUNCTION - ENTITY_TYPE_SNOWFLAKE_SEMANTIC_VIEW - ENTITY_TYPE_REDSHIFT_TABLE - ENTITY_TYPE_REDSHIFT_VIEW - ENTITY_TYPE_REDSHIFT_PROCEDURE - ENTITY_TYPE_REDSHIFT_FUNCTION - ENTITY_TYPE_TABLEAU_EMBEDDED - ENTITY_TYPE_TABLEAU_PUBLISHED - ENTITY_TYPE_TABLEAU_CUSTOM_SQL - ENTITY_TYPE_TABLEAU_TABLE - ENTITY_TYPE_TABLEAU_SHEET - ENTITY_TYPE_TABLEAU_DASHBOARD - ENTITY_TYPE_AIRFLOW_DAG - ENTITY_TYPE_AIRFLOW_TASK - ENTITY_TYPE_CLICKHOUSE_TABLE - ENTITY_TYPE_CLICKHOUSE_VIEW - ENTITY_TYPE_ANOMALY_MONITOR - ENTITY_TYPE_ANOMALY_MONITOR_SEGMENT - ENTITY_TYPE_SQLTEST_TEST - ENTITY_TYPE_RECON_SUITE - ENTITY_TYPE_RECON_CASE - ENTITY_TYPE_POSTGRES_TABLE - ENTITY_TYPE_POSTGRES_VIEW - ENTITY_TYPE_MYSQL_TABLE - ENTITY_TYPE_MYSQL_VIEW - ENTITY_TYPE_DATABRICKS_WAREHOUSE - ENTITY_TYPE_DATABRICKS_TABLE - ENTITY_TYPE_DATABRICKS_VIEW - ENTITY_TYPE_DATABRICKS_JOB - ENTITY_TYPE_DATABRICKS_JOB_TASK - ENTITY_TYPE_DATABRICKS_NOTEBOOK - ENTITY_TYPE_DATABRICKS_QUERY - ENTITY_TYPE_DATABRICKS_DASHBOARD - ENTITY_TYPE_SQLMESH_PROJECT - ENTITY_TYPE_SQLMESH_SQL_MODEL - ENTITY_TYPE_SQLMESH_PYTHON_MODEL - ENTITY_TYPE_SQLMESH_EXTERNAL - ENTITY_TYPE_SQLMESH_SEED - ENTITY_TYPE_SQLMESH_AUDIT - ENTITY_TYPE_SQLMESH_UNIT_TEST - ENTITY_TYPE_SQLMESH_ENVIRONMENT - ENTITY_TYPE_SQLMESH_SNAPSHOT - ENTITY_TYPE_DUCKDB_TABLE - ENTITY_TYPE_DUCKDB_VIEW - ENTITY_TYPE_TRINO_TABLE - ENTITY_TYPE_TRINO_VIEW - ENTITY_TYPE_ATLAN_ASSET - ENTITY_TYPE_ATLAN_INTEGRATION - ENTITY_TYPE_COALESCE_PROJECT - ENTITY_TYPE_COALESCE_ENVIRONMENT - ENTITY_TYPE_COALESCE_NODE - ENTITY_TYPE_COALESCE_NODE_TEST - ENTITY_TYPE_COALESCE_JOB - ENTITY_TYPE_CASTORDOC_TABLE - ENTITY_TYPE_CASTORDOC_DASHBOARD - ENTITY_TYPE_CASTORDOC_VIEW - ENTITY_TYPE_CASTORDOC_TILE - ENTITY_TYPE_CASTORDOC_VIZ_MODEL - ENTITY_TYPE_POWERBI_REPORT - ENTITY_TYPE_POWERBI_TILE - ENTITY_TYPE_POWERBI_DATASET - ENTITY_TYPE_THOUGHTSPOT_LIVEBOARD - ENTITY_TYPE_THOUGHTSPOT_WORKSHEET - ENTITY_TYPE_SIGMA_WORKBOOK - ENTITY_TYPE_SIGMA_DATA_MODEL - ENTITY_TYPE_DOMO_PAGE - ENTITY_TYPE_DOMO_DATASET - ENTITY_TYPE_MSSQL_TABLE - ENTITY_TYPE_MSSQL_VIEW - ENTITY_TYPE_ORACLE_TABLE - ENTITY_TYPE_ORACLE_VIEW - ENTITY_TYPE_ATHENA_TABLE - ENTITY_TYPE_ATHENA_VIEW - ENTITY_TYPE_CUSTOM_ENTITY_GENERIC - ENTITY_TYPE_CUSTOM_ENTITY_CUSTOM_TYPE_MIN - ENTITY_TYPE_CUSTOM_ENTITY_CUSTOM_TYPE_MAX securitySchemes: bearerAuth: type: http scheme: bearer ````