Signalcrest
← Back to feed
devtoai

I Thought Building Agent Observability Was a Detector Problem. I Was Wrong.

Improving agent observability

Steady

18

signal score

Cooling

7-day est. ~13

Why this scored 18

every term, weighted
Velocity+0.0 / 40 max

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+10.9 / 25 max

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25 max

How many independent communities are talking about the same entity

Recency+8.4 / 10 max

Decays to zero over 14 days

Saturation penalty1.4 / 30 max

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite18.0

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Outlook

low confidence · estimate, not a guarantee

7-day

~13

range 1115

14-day

~11

range 814

30-day

~10

range 614

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

opentelemetryllmops
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4336877)](https://www.signalcrest.app/topic/dev%3A4336877)

Drop this in a README or blog post — it updates automatically as the score moves.