Technologies/Weaviate/weaviate_backup_store_data_transferred
WeaviateWeaviateMetric

weaviate_backup_store_data_transferred

The total number of bytes transferred during a backup store
Dimensions:None
Available on:DatadogDatadog (1)
Interface Metrics (1)
DatadogDatadog
The total number of bytes transferred during a backup store
Dimensions:None
Sources
weaviate.backup.store.data.transferredgithub.com

Technical Annotations (14)

Configuration Parameters (3)
BACKUP_S3_BUCKET
S3 bucket name for backup storage; verify bucket exists and is accessible
AWS_REGION
AWS region for S3 bucket; must match bucket region to avoid connectivity issues
chunk_sizerecommended: 256
BackupConfigCreate parameter to control block size, though increasing alone doesn't fix the issue
Error Signatures (2)
BlockListTooLongerror code
The block list may not contain more than 50,000 blockslog pattern
CLI Commands (3)
curl --silent --fail --show-error -H 'Content-Type: application/json' -H "Authorization: Bearer $API_KEY" "http://weaviate.weaviate.svc.cluster.local/v1/backups/backup-s3/$backup_id"diagnostic
GET /v1/backups/{provider}monitoring
GET /v1/backups/{provider}/{backupId}monitoring
Technical References (6)
backup-s3component/v1/backups/backup-s3file pathbackup-azurecomponentBackupConfigCreatecomponentshard replica nodescomponentreplicated classescomponent
Related Insights (4)
S3 backup gets stuck in STARTED state indefinitelycritical
▸
Azure backup fails with 50,000 block limit exceededcritical
▸
Backup procedure failed to create shard backups across all replicascritical
▸
Unmonitored backup operations lead to silent failureswarning
▸