One query language.
Every signal.
A monitor is gcQL plus a threshold: the same query that powers your dashboards, watching your system continuously and turning a breach into an issue the moment it happens.
One language, six data types.
Logs, metrics, traces, events, entities, and monitors, queried the same way.
Query across tables, not just within one.
The from keyword lets a single gcQL query span multiple tables instead of forcing separate lookups.
Nothing is a black box.
Every query, human-written or agent-generated, is visible, editable, and reusable. It can be written as raw gcQL code, not just built through a UI.
Most platforms make you learn seven query languages
Traditional observability stacks accumulate a separate query model per data type: one for logs, another for metrics, another for traces. That means constant translation, for engineers and for AI agents trying to investigate an issue alike.
The from keyword, and gcQL as real code
gcQL added a from keyword so a single query can span multiple tables instead of requiring separate lookups stitched together after the fact. The Monitor Wizard now has a gcQL code mode, so instead of only building a monitor through guided steps, you can write and validate the underlying query directly.
Multi-source joins and stronger trace search
Recent gcQL releases added multi-source joins, stronger trace search, in() support, new pipes, automatic aliasing, and time-based filtering - the connective tissue for correlating signals that used to require separate tools.
What the AI agent runs, you can read
gcQL isn't only for people typing queries by hand - it's what Agent Mode uses under the hood to investigate. Every query the agent runs is visible in the relevant product page, and can be modified, saved as a monitor, or turned into a dashboard widget.
????????????????????????
- Powers both native dashboards/monitors and Agent Mode output
- Recent releases: from-keyword cross-table queries, gcQL code mode in Monitors, grok filter operator, multi-source joins, LangChain integration
FAQ starters
Common questions about gcQL and how it fits into groundcover.
???
Yes. The from keyword lets a single gcQL query span multiple tables without separate lookups stitched together after the fact.
Write and validate the underlying query directly. You see exactly what the monitor will evaluate before saving it - no save-and-pray.
No. Agent Mode uses gcQL natively. Every query it runs is visible in the relevant product page and can be edited, saved as a monitor, or turned into a dashboard widget.
Yes. Any query you write - or one an agent generated - can be saved as a monitor or pinned as a dashboard widget directly from the query editor.
It connects LangChain-based workflows to gcQL, so agents built outside groundcover can run queries against your observability data using the same unified query language.
???
Explore More groundcover products
Discover additional groundcover capabilities that work seamlessly with Synthetics.
Application Performance Monitoring
Gain end-to-end visibility into application performance. Identify and resolve issues instantly with zero code changes.
Dashboards
Ask Agent Mode for a dashboard and get a fully populated, live board on the first pass. Every panel stays there next Tuesday at 3am, shared with the whole team, whether or not you're in the room.
Monitors
A monitor is gcQL plus a threshold: the same query that powers your dashboards, watching your system continuously and turning a breach into an issue the moment it happens.
Observability
for what comes next.
Start in minutes. No migrations. No data leaving your infrastructure. No surprises on the bill.
.svg)