DatabaseResourceFeed

import type { DatabaseResourceFeed } from "https://googleapis.deno.dev/v1/redis:v1.ts";

DatabaseResourceFeed is the top level proto to be used to ingest different database resource level events into Condor platform. Next ID: 13

interface DatabaseResourceFeed {

backupdrMetadata?: BackupDRMetadata;

configBasedSignalData?: ConfigBasedSignalData;

databaseResourceSignalData?: DatabaseResourceSignalData;

feedTimestamp?: Date;

feedType?:

| "FEEDTYPE_UNSPECIFIED"

| "RESOURCE_METADATA"

| "OBSERVABILITY_DATA"

| "SECURITY_FINDING_DATA"

| "RECOMMENDATION_SIGNAL_DATA"

| "CONFIG_BASED_SIGNAL_DATA"

| "BACKUPDR_METADATA"

| "DATABASE_RESOURCE_SIGNAL_DATA";

observabilityMetricData?: ObservabilityMetricData;

recommendationSignalData?: DatabaseResourceRecommendationSignalData;

resourceHealthSignalData?: DatabaseResourceHealthSignalData;

resourceId?: DatabaseResourceId;

resourceMetadata?: DatabaseResourceMetadata;

skipIngestion?: boolean;

}

§Properties

backupdrMetadata?: BackupDRMetadata

[src]

BackupDR metadata is used to ingest metadata from BackupDR.

configBasedSignalData?: ConfigBasedSignalData

[src]

Config based signal data is used to ingest signals that are generated based on the configuration of the database resource.

databaseResourceSignalData?: DatabaseResourceSignalData

[src]

Database resource signal data is used to ingest signals from database resource signal feeds.

feedTimestamp?: Date

[src]

Required. Timestamp when feed is generated.

[src]

Required. Type feed to be ingested into condor

observabilityMetricData?: ObservabilityMetricData

[src]

recommendationSignalData?: DatabaseResourceRecommendationSignalData

[src]

resourceHealthSignalData?: DatabaseResourceHealthSignalData

[src]

resourceId?: DatabaseResourceId

[src]

Primary key associated with the Resource. resource_id is available in individual feed level as well.

resourceMetadata?: DatabaseResourceMetadata

[src]

skipIngestion?: boolean

[src]

Optional. If true, the feed won't be ingested by DB Center. This indicates that the feed is intentionally skipped. For example, BackupDR feeds are only needed for resources integrated with DB Center (e.g., CloudSQL, AlloyDB). Feeds for non-integrated resources (e.g., Compute Engine, Persistent Disk) can be skipped.