Where do I see whether the trigger for a disk filling up fired and which run it woke?

Tares shows you both on the trigger’s page and under Firings, and the run it woke appears in Activity and under the agent’s Runs. Open the trigger for a disk filling up to see each firing, then follow it to the run in Activity. If nothing fired, check that the trigger’s sources and filters match the events that arrived.

How it works

A trigger evaluates as events arrive. When its sources, filters and condition match, it fires, and each firing wakes the agent subscribed to that trigger. Tares records the whole chain, so you can read it from either end.

• The trigger’s page lists its firings. In a local Tares the page for a trigger named incident is at http://127.0.0.1:8787/triggers/incident, and your trigger for a disk filling up follows the same pattern with its own name.
• Firings is the console list of firings across triggers.
• Activity shows a firing and the run it woke as one thread. You find it under Setup, then Advanced setup.
• Agents, then your agent, then Runs lists every run that agent has made, including the one the firing woke.
• Findings the agent writes land on the service’s timeline in Explore. They also appear on the project’s Overview under What the agents found, with a headline and the next step.

The condition of a trigger is an aggregate over a window, for example a sum over 1m per service. A trigger fires when that condition holds for events that pass its filters, so the events have to carry the labels and fields the trigger reads.

Set it up

1. Start Tares and open the console if it is not already running.

tares up

2. Open Triggers and pick the trigger for a disk filling up. Its page shows its firings. Each firing is a moment the condition held.
3. Open Firings to see the same firings next to those of your other triggers.
4. To see the run a firing woke, go to Setup, then Advanced setup, then Activity. The firing and the run it woke appear as one thread.
5. To see every run for the agent, go to Agents, open the agent subscribed to the trigger, and open Runs.
6. To read the conclusion, open the project’s Overview and look under What the agents found, or open the service’s timeline in Explore.
7. If the trigger has no firings, check why it did not match:
   • Open Explore for the service and confirm the events you expect are there, with the labels the trigger uses.
   • Confirm the trigger’s sources list includes the source that carries those events.
   • Check the trigger’s filters. Each filter has a field, an op and a value, and the events must satisfy them.
   • Check the condition: its aggregate, predicate and window, and that events share the key label, such as service, that the trigger groups by.
8. Confirm an agent is subscribed to the trigger. A firing wakes the agents subscribed to it, so a trigger without a subscriber fires and wakes no run.

The AI SRE guide walks through the same chain with a demo trigger, where you can watch a firing, its run and the finding appear in this order.

What you get

• A yes or no answer on whether the trigger fired, read from its page or from Firings.
• The exact run the firing woke, found by following the thread in Activity or by opening the agent’s Runs.
• The agent’s finding on the service’s timeline and on the project Overview, so you can read what it concluded without opening the run.
• A short checklist when the trigger did not fire: the sources, the filters and the condition, each checked against the events that actually arrived.

Because a trigger evaluates as events arrive, a trigger with no firings is not broken. It means no arriving events met its sources, filters and condition so far. Looking at the events in Explore tells you which part to change.

When something else fits

• If you want to read the evidence yourself rather than check firings, connect an MCP client with tares mcp and ask it what happened to the service. It reads the same correlated timeline, including any finding the agent wrote.
• If the trigger fired but the run does not appear under the agent you expect, check which agent is subscribed to the trigger, then look at that agent’s Runs.
• If the events never reach Tares, the fix is on the source side. Check the source’s configuration and its labels before you change the trigger.

Related