Open in ChatGPTOpen in Claude

Deprecation of Legacy Explore

Published: September 27, 2026

Effective: December 15, 2026

Deprecation notice

Coralogix will retire Legacy Explore on December 15, 2026. On that date, both the V1 Legacy Explore screens and all v1 permissions are removed from the Coralogix interface, and Legacy Explore (v1) is no longer accessible.

Legacy Explore is deprecated in favor of Explore, which brings logs, spans, and your other datasets into one investigation surface. In the sidebar, Legacy Explore appears as Explore (Legacy), and Explore appears as the Logs and Tracing entries.

No action is needed from you. You are moved to the new Explore automatically: opening a Legacy Explore link carries your query into Explore, so there is nothing to rebuild by hand for day-to-day investigations.

The exception is automation. Rebuild any bookmark, runbook, alert webhook, or script that builds a legacy /query-new/ link, because those links stop working once the screens are removed on December 15, 2026 and redirect to the new Explore.

Why this is happening

Explore covers the investigation workflows you run in Legacy Explore today, and adds capability the legacy screens were not built for:

• One surface for every dataset: query logs, spans, system datasets, and your own custom datasets from the same screen, instead of switching between a logs screen and a tracing screen. See Select a dataset.
• Builder and DataPrime side by side: compose a query with chips in the Builder, or switch to DataPrime for advanced queries, on the same results.
• A fields panel that shows value counts: see which values exist and how often before you commit to a filter. Every action from the fields panel is reflected consistently in the query, not a separate state. See Filter with fields.
• Parallel investigations in tabs: run several queries at once and compare them, then save and share the view. See Explore views, tabs, and queries.
• Templates in the same query: log patterns are a tab on your results rather than a separate screen. See Templates.
• Readable deep links: every parameter in the URL is plain text, so links are easy to read, hand-edit, and generate. See Deep links and URL parameters.
• Visualize: view query results from several perspectives, as graphs to quickly identify trends and anomalies over time, alongside grouping and aggregating the data across multiple visualizations.
• Builder query: query your data simply, with grouping, aggregation, ordering, and filtering, and see it reflected directly across multiple visualization and grid options, on top of views and the grid.

What's affected

The following Legacy Explore screens will be removed on December 15, 2026:

Legacy Explore screen	URL path
Logs	/query-new/logs, /query-new/archive-logs
Log Templates	/query-new/loggregation, /query-new/archive-loggregation
Tracing	/query-new/tracing

This affects:

• Teams that query logs, log templates, or traces from the legacy screens.
• Roles and API keys that rely on a v1 permission for Legacy Explore. All v1 permissions are removed on the same date.
• Bookmarks and shared links that point to one of the URLs listed above.
• Runbooks, alert webhooks, dashboard links, or scripts that build one of those URLs.

LiveTail and Visual Explorer are not part of this deprecation and continue to work as they do today, including the /query-new/visual-explorer URL.

Moving to Explore

Find your data in Explore

In Coralogix, select Explore, then Logs or Tracing. Select the dataset that matches the tier you queried in Legacy Explore:

• Frequent Search: select the frequentsearch/logs or frequentsearch/spans dataset.
• Archive: select default/logs or default/spans, which Explore selects by default.

See Select a dataset for the full list, including system datasets and your own custom datasets.

Carry your current query over

In Legacy Explore, select Try it now in the banner at the top of the screen. Your query and filters carry into Explore, so there is nothing to rebuild by hand.

After you have done that once, opening a legacy Explore link, such as a bookmark, a shared link, or a page refresh, lands you in Explore with the same query. If a link carries something Explore cannot express, you stay on Legacy Explore instead, so your query never changes silently.

Check your saved views

Open Explore and confirm the views you rely on are there. See Saved views for creating, managing, and sharing them. If a view you depend on is missing, contact us before the effective date.

Rebuild automation that builds legacy links

Day-to-day investigation needs no changes, but automation is the exception. Rebuild any bookmark, runbook, alert webhook, or script that builds a /query-new/ URL against Explore's URL parameters, because those links redirect to the new Explore once the screens are removed. Explore's parameters are human-readable, such as ?query=…&dataset=…&duration=…, so a link is straightforward to write by hand or generate programmatically. See Deep links and URL parameters.

Common tasks and where to find them in Explore

Task in Legacy Explore	Use this in Explore
Search logs with Lucene	Search logs and spans
Filter with the metadata sidebar (application, subsystem, severity)	Filter with fields
Build a query without writing syntax	Query builder
Run a DataPrime query	DataPrime query
Query the Frequent Search tier	The frequentsearch/logs dataset, see Select a dataset
Query archived logs	The default/logs dataset, see Select a dataset
Work with log templates (Loggregation)	Templates
Query spans and traces	Explore spans
Group and aggregate results	Overview tab
Chart your results over time	Time-series chart
Select columns and act on a row	Logs table
Save, share, and reopen a view	Explore views, tabs, and queries
Export query results	Export data

Saved-view API

The legacy saved-view API behind Legacy Explore, LegacyViewsService, is retired on December 15, 2026, the same day as Legacy Explore. For example:

• https://ng-api-grpc.eu2.coralogix.com/com.coralogixapis.views.v1.services.LegacyViewsService/CreateLegacyView
• https://ng-api-grpc.eu2.coralogix.com/com.coralogixapis.views.v1.services.LegacyViewsService/ListTeamLegacyViews

Migrate any integration that calls this API to the Saved Views API, SavedViewsService, before then. For example:

• https://api.eu2.coralogix.com/com.coralogix.saved_views.v1.SavedViewsService/CreateSavedView
• https://api.eu2.coralogix.com/com.coralogix.saved_views.v1.SavedViewsService/ListSavedViews

These endpoints use your Coralogix domain. Select your region using the domain selector at the top of the page.

What will happen after December 15, 2026?

• The Legacy Explore screens are removed from the Coralogix interface, and Legacy Explore (v1) is no longer accessible.
• All v1 permissions are removed from the interface.
• The legacy saved-view API (LegacyViewsService) is retired. Move integrations to the Saved Views API (SavedViewsService).
• Bookmarks, runbooks, and scripts that build a legacy /query-new/ logs, templates, or tracing URL redirect to the new Explore instead of opening the old screens. Rebuild any automation that depends on those links.
• Log and trace investigation continues in Explore.
• LiveTail and Visual Explorer are unaffected.
• There is no impact on your data, ingestion, retention, alerts, or dashboards.

Additional resources

• Explore
• Select a dataset
• Explore spans
• Explore views, tabs, and queries
• Deep links and URL parameters

Need help?

Our team is here to help you migrate smoothly.

Is something blocking your move to Explore, such as a workflow you cannot reproduce or a reason your team cannot migrate by December 15, 2026? Reach out via our 24/7 in-app support, or contact your Account Manager or Technical Account Manager before the deadline, and we'll guide you through the transition.