Telemetry and Logging Disclosure
In BYOC, warehouse compute and customer warehouse storage run in your cloud environment and form the customer data plane. VeloDB can export operational telemetry to the VeloDB control plane for service monitoring, health management, capacity planning, incident response, and platform operations.
This page does not specify where every control-plane, support, or audit record is stored or processed, nor does it cover customer-configured notification destinations. For deployment-specific data-processing information, contact VeloDB Support.
VeloDB does not export customer table data, database contents, query results, customer-managed object storage contents, backups, or customer-managed encryption keys from the customer environment. Telemetry collection is intentionally limited to operational information necessary to operate and support the service.
Categories of Information Exported
Infrastructure Metrics
VeloDB collects a limited set of infrastructure metrics from BYOC deployments for monitoring, alerting, capacity planning, and availability management. These metrics may include CPU, memory, storage, disk I/O, and network utilization, as well as node health, service availability, cluster topology, and capacity indicators.
VeloDB uses these operational metrics only to assess deployment health and performance. They do not contain customer business data, database contents, table data, or query results.
Service Metrics
VeloDB also collects aggregated service metrics for operational monitoring and reliability management. Examples include query throughput, latency distributions, error rates, replication status, storage utilization, and warehouse or cluster health indicators.
Service metrics are aggregated operational statistics and are used for capacity management, performance monitoring, and SLA tracking. These metrics do not include query text, query execution plans, query results, table names, schema names, or other customer business data.
Diagnostic Logs (Optional)
Customers may optionally enable forwarding of WARNING- and ERROR-level diagnostic logs for troubleshooting and service reliability investigations. These logs may include service startup failures, configuration validation issues, replication failures, storage subsystem errors, software upgrade failures, and application exception stack traces.
Diagnostic logs are intended solely for incident investigation, root cause analysis, and service improvement activities. VeloDB does not intentionally collect query text, query execution plans, table names, schema names, database contents, or query results through diagnostic log forwarding.
Metadata Disclosure
Operational telemetry and diagnostic events may contain limited metadata needed to identify and manage deployed resources. Examples include cluster, warehouse, and node identifiers; software versions; cloud provider and region information; infrastructure resource identifiers; operational timestamps; service health indicators; and error codes.
This metadata is used exclusively for operational management and support purposes. Customer business data is not intentionally collected as part of telemetry or diagnostic events.
Data Not Exported
As part of its data minimization approach, VeloDB does not export the following categories of information from BYOC environments to the VeloDB control plane:
- Table data and database contents
- Query results
- Query text and query execution plans
- Table names and schema names
- Customer-managed object storage contents
- Customer-managed encryption keys
- Database backups
- Customer application data
These categories are not part of the standard telemetry described on this page.
Log Forwarding Controls
VeloDB supports two telemetry modes for different security and compliance requirements:
| Mode | Data exported |
|---|---|
| Metrics Only | Infrastructure and service metrics; no diagnostic logs |
| Metrics and Diagnostic Logs | Infrastructure metrics, service metrics, and WARNING- and ERROR-level diagnostic logs |
Customers may request that diagnostic log forwarding be disabled entirely for production environments.
Retention
VeloDB retains telemetry and diagnostic information only to the extent necessary to support operational monitoring, incident investigation, service reliability management, and applicable compliance requirements.
Under normal operations, VeloDB retains telemetry and diagnostic information for no more than 15 days. At the end of the retention period, VeloDB deletes or otherwise removes the information from its operational systems in accordance with its data retention and disposal procedures.
Telemetry and diagnostic information is not retained for purposes unrelated to service operations, support activities, or compliance obligations.
Processing Region
Telemetry information is processed only within VeloDB-operated cloud environments and is not shared with third parties except where necessary to provide the service or where required by law.
For processing-region and deployment-specific handling details, contact VeloDB Support.
Encryption
Data in Transit
Telemetry and control-plane communications between a BYOC deployment and the VeloDB control plane are protected by end-to-end application-layer TLS.
This traffic also travels over private cloud networking and does not traverse the public internet. Equivalent private connectivity mechanisms are used across the supported cloud platforms. Protocol-level encryption and a private network path together protect this communication: TLS keeps the payload encrypted end to end, and private connectivity keeps the traffic off the public internet.
Data at Rest
Telemetry information stored within VeloDB-operated environments is encrypted at rest using cloud-provider-managed encryption controls and associated storage encryption mechanisms.
Access Controls
Role-based access control (RBAC) and the principle of least privilege govern access to telemetry information. Access is limited to authorized VeloDB operations and support personnel whose roles require it.
Administrative access to telemetry systems is logged and subject to audit controls.
Redaction and Data Minimization
VeloDB limits telemetry collection to the information needed to operate, monitor, maintain, and support the service.
Customer business data is not intentionally collected, processed, or exported through normal telemetry or diagnostic logging. Collection is designed to minimize the information exported while preserving the visibility needed for service reliability and customer support.