---
title: Full Text Search
description: Find content in inputs and outputs of your traces and observations with full text search.
date: 2025-05-19
author: Max
ogVideo: https://static.langfuse.com/docs-videos/2025-05-19-ft-search.mp4
badge: Launch Week 3 🚀
showOgInHeader: false
canonical: https://langfuse.com/docs/observability/features/full-text-search
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/observability/features/full-text-search) and the API/SDK reference (https://api.reference.langfuse.com).

<iframe
  width="100%"
  src="https://www.youtube-nocookie.com/embed/9gPDNtQj1uU"
  title="Full Text Search Tutorial"
  frameBorder="0"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  className="aspect-video rounded border mt-6"
  allowFullScreen
></iframe>

**Day 1 of [Launch Week 3](/blog/2025-05-19-launch-week-3)** is here, and we're excited to announce the launch of full-text search. This feature has received one of the highest numbers of upvotes in our [feature requests](https://github.com/orgs/langfuse/discussions/939), and we are thrilled to make it available. Finding all occurrences of a specific keyword or phrase across your Langfuse traces and observations can be extremely helpful.

See the video above for a quick tutorial.

## Learn more

- [Full-Text Search](/docs/observability/features/full-text-search)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2025-05-19-full-text-search.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.