Skip to main content
Search your team’s queries to learn from past investigations. Need to understand how a teammate debugged a similar issue? Want to find that query you built last week? Query History tracks every query run by your team, making it easy to learn from past investigations, reuse effective queries, and build on your team’s collective knowledge.

​
What is Query History?

Query History is a searchable record of all queries run by your Team across all Datasets. When you open Query History, you can browse recent activity, search for specific queries, or explore saved queries from yourself and your teammates.
Query History page showing recent team activity (screenshot)

​
How It Works

Query History tracks all queries across all Datasets in your team. Search works across multiple fields, and results are limited to your selected Environment. Query History searches across:
  • Titles
  • Descriptions
  • Query fields
  • Team member email addresses
  • Time
Queries with detailed names and descriptions are easier to find because they provide more search context. To narrow results, use search prefixes.

​
Scope

Query History shows queries from the Environment selected in your environment selector and searches across all Datasets in that Environment. To explore query history for a different Environment, switch Environments using the environment selector.

​
Searching Query History

Use Query History search to find queries you built in the past, discover how teammates solved problems, or replay the debugging steps from an incident.
  1. Select History () from the navigation menu.
  2. Enter your search terms in the search bar.
    Add search prefixes to narrow your results.
  3. Select Search.
The screen refreshes and shows the queries that match your criteria.

​
Search Prefixes

Add prefixes to narrow the results of your search. You can use each prefix once per search.
SyntaxDescriptionExample
user:meShow only your queries.user:me
user:email_addressShow queries run by a specific user.user:bee@example.com
before:yyyy-mm-ddShow queries run before this date.before:2022-02-08
after:yyyy-mm-ddShow queries run after this date.after:2022-03-13
dataset:dataset_slugShow queries from a specific Dataset. The dataset slug is the URL-friendly identifier for your dataset that appears in Honeycomb URLs.dataset:frontend-production
This example searches the frontend dataset for queries run after a specific date:
Query History page showing a query history search (screenshot)

​
Saving a Query

Save queries to My Saved Queries for personal reuse. To save a query:
  1. Select Query () from the navigation menu.
  2. Build your query in Query Builder, and select Run Query.
  3. From the Save query dropdown, choose My Saved Queries.
  4. In the modal, enter query details:
    FieldDescription
    Query nameName of your query.
    DescriptionDescription of the query.
    Give your queries meaningful names and detailed descriptions to make them easier to find. Explain what you’re investigating, why you ran the query, what you found, or what problem it solves.
  5. Select Save query.
Your query is saved to My Saved Queries.

​
Best Practices

  • Use descriptive query names: Give queries meaningful names that explain what you’re investigating. “API latency spike investigation” is more useful than “query 1.”
  • Add context in descriptions: Explain why you ran the query, what you found, or what problem it solves.
  • Save important queries: Don’t rely on browsing Recent Queries to find queries you’ll need again. Save them to My Saved Queries.
  • Search by user: Use the user: prefix to see how specific teammates approach problems or to find queries from subject matter experts.
  • Combine prefixes: Narrow results by combining prefixes, like user:me after:2025-06-01 dataset:frontend to find your recent frontend queries.