Cloud Auto-Sync & Archiving
Automatically offload encrypted daily performance telemetry, Core Web Vitals datasets, and SLA audit summaries directly into your personal cloud storage.
Zero-Knowledge AES-256-GCM Cryptography
Your credentials are never stored in plaintext
When you connect your Google Drive, Dropbox, or AWS S3 bucket, Pingzo encrypts all OAuth access tokens, refresh keys, and IAM secret keys at the application level using AES-256-GCM (Galois/Counter Mode). Each record is encrypted with a unique, cryptographically random 16-byte Initialization Vector (IV) and protected with an authentication tag before it touches the database.
1. Google Drive Integration (2-Minute Setup)
Directly stream daily CSVs to a dedicated Google Drive folder
Pingzo requests the restricted .../auth/drive.file scope. This grants Pingzo permission only to files and folders created by Pingzo (e.g. your Pingzo Backups folder). Pingzo has zero access to your personal documents, spreadsheets, or existing Google Drive files.
Step-by-Step Instructions:
- Open the Google OAuth 2.0 Playground .
- In the left panel under Step 1: Select & authorize APIs, scroll down to Drive API v3.
- Check the box for
https://www.googleapis.com/auth/drive.file. - Click the blue Authorize APIs button at the bottom of the left column, and sign in with your Google account.
- Under Step 2: Exchange authorization code for tokens, click Exchange authorization code for tokens.
- Copy the
access_tokenvalue (or the entire JSON block), return to your Pingzo Dashboard, paste it into the token field, and click Save & Encrypt Credentials.
Once connected, click Test Sync Now. Pingzo will immediately verify authorization, automatically create a Pingzo Backupsfolder in your Google Drive if it doesn't exist, and upload your first live CSV report in under 3 seconds.
2. Dropbox Integration
Archive telemetry directly to your scoped Dropbox App folder
Step-by-Step Instructions:
- Visit the Dropbox App Console .
- Click Create App and select:
- API: Scoped access
- Type of access: App folder (isolated sandbox directory)
- Name your app: e.g.
Pingzo Telemetry Backups
- In the Permissions tab, check
files.content.writeandfiles.content.read, then click Submit. - In the Settings tab, scroll down to OAuth 2: Generated access token and click Generate.
- Copy the generated token (
sl.u...) and paste it into Pingzo under Connect Dropbox.
3. AWS S3 & S3-Compatible Storage
Stream datasets to AWS S3, Cloudflare R2, MinIO, or Wasabi
Minimal Least-Privilege IAM Policy:
Attach the following IAM JSON policy to your dedicated backup user or role:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject"
],
"Resource": "arn:aws:s3:::your-bucket-name/*"
}
]
}Cloudflare R2 Setup:
In the Cloudflare Dashboard, go to R2 > Manage R2 API Tokens. Set Endpoint URL to:https://<ACCOUNT_ID>.r2.cloudflarestorage.com
MinIO & Wasabi:
Provide your custom host endpoint URL in the Endpoint field (e.g. https://s3.wasabisys.com) along with your API access and secret keys.
Exported Datasets & Schema Breakdown
Every automated sync and on-demand export delivers two dedicated, RFC-4180 compliant CSV files with separate Date and Time columns for instant filtering and pivot table analysis:
File 1: Monitors Summary (pingzo_monitors_summary_YYYY-MM-DD.csv)
| Column Name | Type | Description |
|---|---|---|
| Monitor ID | String | Unique system identifier for the monitor check. |
| Name & Target / URL | String / URL | Friendly monitor name and destination URL/host address. |
| Type & Port | String / Int | Protocol type (http, port_tcp, port_udp) and socket port. |
| Current Status | Enum | Live health state (up, down, paused). |
| Total Outages & Downtime | Integer / Duration | Cumulative incidents count and formatted total downtime (42m 15s). |
| Calculated Uptime % | Percentage | Calculated SLA uptime availability percentage (e.g. 99.94%). |
| SSL Expiry & Days Remaining | Date / String | Certificate expiration date and remaining validity countdown. |
| Created Date & Time (UTC) | Date / Time | Dedicated calendar date (YYYY-MM-DD) and UTC time (HH:mm:ss) columns. |
File 2: Incident & Recovery Audit Log (pingzo_incident_audit_log_YYYY-MM-DD.csv)
| Column Name | Type | Description |
|---|---|---|
| Incident ID | String | Unique identifier for the specific downtime incident event. |
| Outage Start Date & Time (UTC) | Date / Time | Calendar date (YYYY-MM-DD) and exact UTC timestamp (HH:mm:ss) downtime began. |
| Recovery Date & Time (UTC) | Date / Time | Exact UTC date and time service recovered, or ONGOING for active incidents. |
| Outage Duration | Duration / Seconds | Human-readable duration (9m 35s) plus raw seconds (575) for spreadsheet formulas. |
| Error Cause / Diagnostic | String | Root failure reason (e.g. HTTP 502 Bad Gateway or TCP Socket Timeout). |
| Max Escalation Stage | String | Highest on-call escalation tier triggered (Stage 1, Stage 2, or Stage 3). |
| Resolved By | String | Attribution (Auto-recovered by probe or responder name). |
File 3: RUM Web Vitals Analytics (pingzo_rum_vitals_analytics_YYYY-MM-DD.csv)
| Column Name | Type | Description |
|---|---|---|
| Site ID & Domain | String / Domain | Unique RUM site identifier and verified domain address. |
| Verification Status & Method | String / Enum | Ownership status (VERIFIED) and method (script, meta_tag, dns_txt). |
| Record Date & Hour (UTC) | Date / Time | Dedicated calendar date (YYYY-MM-DD) and hourly window start (HH:mm:ss). |
| Pageview / Sample Count | Integer | Total real visitor telemetry beacons captured in that hourly window. |
| Core Web Vitals P75 & Ratings | Float / Rating | Google P75 standards for LCP, TTFB, CLS, and INP with official ratings (Good, Needs Work, Poor). |
| Rolling Averages | Float | Mathematical rolling averages for LCP, TTFB, CLS, and INP across the hour. |
| Top Devices & Browsers | JSON String | Aggregated visitor client breakdown (e.g. desktop: 280, mobile: 170 | Chrome: 310, Safari: 140). |
| Site Created Date & Time (UTC) | Date / Time | Dedicated domain registration date and UTC creation timestamp. |
Frequently Asked Questions & Troubleshooting
Why did I receive a 401 UNAUTHENTICATED error on test sync?
Google Drive and Dropbox OAuth access tokens expire over time. If you receive a 401 error, simply click the Trash icon to disconnect the integration, generate a fresh token from the OAuth Playground or App Console, and reconnect.
What time does the automated nightly sync execute?
Automated daily offloading runs at 03:00 UTC every night. Weekly backups execute every Sunday at 03:00 UTC.
Can I export a manual CSV without connecting a cloud provider?
Yes! Click the Export Live CSV Snapshot button at the top of the Cloud Auto-Sync dashboard tab to immediately download your workspace telemetry dataset directly to your local computer.