---
date: 2026-09-02
title: Create alerts for evaluators
description: Create score and cost alerts directly from evaluator pages and review every alert linked to an evaluator.
author: Tobias Wochinger
ogVideo: https://static.langfuse.com/changelog-videos/2026-09-02-evaluator-alerts.mp4
canonical: /docs/observability/features/alerts#evaluator-alerts
---

> **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/alerts#evaluator-alerts) and the API/SDK reference (https://api.reference.langfuse.com).

You can now create and manage alerts directly from the evaluator workflow. Langfuse prefills the metric and filters, so you only need to set the threshold and choose how your team should be notified.

- Get notified when an evaluator's average numeric or Boolean score drops below your quality target.
- Watch categorical score counts for changes in topics, failures, or policy outcomes.
- Set a cost threshold for one LLM-as-a-Judge evaluator or for all evaluators combined.

- [Evaluator concepts](/docs/evaluation/core-concepts#monitor-evaluator-results)
- [Alerts docs](/docs/observability/features/alerts)

<!-- 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/2026-09-02-evaluator-alerts.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>.