You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logs.all Management API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement. Log querying moves to a new ClickHouse-backed logs endpoint. The new endpoint accepts ClickHouse SQL only. It returns every source through a single unified logs table instead of a separate table per source.
How Do I Know if This Impacts Me?
You are impacted only if you query the logs.all Management API endpoint (.../analytics/endpoints/logs.all). This includes any scripts, integrations, or tooling that call it directly.
If you do not call this endpoint, no action is needed. Using logs through the dashboard Logs Explorer is not affected.
Convert your SQL to the ClickHouse dialect. The endpoint only accepts ClickHouse SQL.
Filter by source_name instead of selecting a source table. All sources now live in one logs table. Filter to a specific source in the WHERE clause.
Before (query a source table directly):
SELECTtimestamp, event_message
FROM edge_logs
ORDER BYtimestampDESCLIMIT100
After (filter the unified stream by source_name):
SELECTtimestamp, event_message
FROM logs
WHERE source_name ='edge_logs'ORDER BYtimestampDESCLIMIT100
Any query that previously targeted a specific table must now add a source_name filter in its WHERE clause.
Accessing Nested Fields
Nested fields move from the metadata array to a flat log_attributes map. Before, you added one CROSS JOIN unnest() per level of nesting to reach a field. Now you read the field directly from log_attributes with map key access. The joins go away.
Before (unnest each level of metadata):
SELECTtimestamp, request.method, header.x_real_ipFROM edge_logs
CROSS JOIN unnest(metadata) AS m
CROSS JOIN unnest(m.request) AS request
CROSS JOIN unnest(request.headers) AS header
After (read from the log_attributes map):
SELECTtimestamp,
log_attributes['request.method'] AS method,
log_attributes['request.headers.x_real_ip'] AS x_real_ip
FROM logs
WHERE source_name ='edge_logs'
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The
logs.allManagement API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement. Log querying moves to a new ClickHouse-backedlogsendpoint. The new endpoint accepts ClickHouse SQL only. It returns every source through a single unifiedlogstable instead of a separate table per source.How Do I Know if This Impacts Me?
You are impacted only if you query the
logs.allManagement API endpoint (.../analytics/endpoints/logs.all). This includes any scripts, integrations, or tooling that call it directly.If you do not call this endpoint, no action is needed. Using logs through the dashboard Logs Explorer is not affected.
What Should I Do?
analytics/endpoints/logs.alltoanalytics/endpoints/logs.source_nameinstead of selecting a source table. All sources now live in onelogstable. Filter to a specific source in theWHEREclause.Before (query a source table directly):
After (filter the unified stream by
source_name):Any query that previously targeted a specific table must now add a
source_namefilter in itsWHEREclause.Accessing Nested Fields
Nested fields move from the
metadataarray to a flatlog_attributesmap. Before, you added oneCROSS JOIN unnest()per level of nesting to reach a field. Now you read the field directly fromlog_attributeswith map key access. The joins go away.Before (unnest each level of
metadata):After (read from the
log_attributesmap):Timeline
logs.allendpoint removed for all projectsLearn More
logsendpoint and its parametersBeta Was this translation helpful? Give feedback.
All reactions