Skip to content

fix: Correct summary of scheduled queries option for live data #871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sean-rose merged 2 commits into from
Sep 19, 2025
Merged

fix: Correct summary of scheduled queries option for live data #871

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b0f5cc
fix(docs): Correct summary of scheduled queries option for live data.
sean-rose Sep 19, 2025
ac4047c
fix: Compact table.
sean-rose Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions src/cookbooks/live_data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@ Use cases, such as real-time monitoring, dashboards, or personalized user experi

## Options for working with Live Data

| Option | Recommended Use Case | Data Size/Complexity | Latency | Setup Complexity |
| -------------------------------------- | ------------------------------------------------------ | ---------------------------------------------------- | --------- | ---------------- |
| 1. Querying Live Tables Directly | Small datasets or infrequent, simple queries | Low | 10-30 min | Low |
| 2. Scheduled queries | Medium | Periodic updates (e.g., hourly/daily) for dashboards | Medium | 1h or more | Medium |
| 3. Using Materialized Views | Large datasets, complex queries with low-latency needs | Medium to High | 10-30 min | Medium to High |
| 4. Dataflow | Very low-latency streaming for large datasets | High | <10 min | High |
| 5. Cloud function with Pub/Sub trigger | Low-latency for smaller subsets of data | Medium | <10 min | Medium to High |
| Option | Recommended Use Case | Data Size/Complexity | Latency | Setup Complexity |
| -------------------------------------- | ------------------------------------------------------ | -------------------- | ---------- | ---------------- |
| 1. Querying Live Tables Directly | Small datasets or infrequent, simple queries | Low | 10-30 min | Low |
| 2. Scheduled queries | Periodic updates (e.g., hourly/daily) for dashboards | Medium | 1h or more | Medium |
| 3. Using Materialized Views | Large datasets, complex queries with low-latency needs | Medium to High | 10-30 min | Medium to High |
| 4. Dataflow | Very low-latency streaming for large datasets | High | <10 min | High |
| 5. Cloud function with Pub/Sub trigger | Low-latency for smaller subsets of data | Medium | <10 min | Medium to High |

Live ping tables are the final destination for the telemetry ingestion pipeline. Incoming ping data is loaded into these tables approximately every 10 minutes, though a delay of up to 30 minutes is normal. Data in these tables is set to expire after 30 days.

Expand Down