Signals
| Signal | Description |
|---|---|
| Disproportionate volume | One event shape represents a large share of a service’s logs. |
| Generic message text | Messages such as Incoming request, Processing item, or Handling request repeat with little diagnostic context. |
| Unconditional emission | The log appears on every request, item, or loop iteration. |
| Healthy-state volume | The pattern occurs during normal service operation, not only during incidents. |
Example
- Middleware logging
- Loop logging
- Before
- After
Recommended enforcement
Open PRs
Remove, relocate, or condition the log statement in code.
Create tickets
Ask the owning team to review the high-volume logging pattern.
Detection notes
Tero identifies hot-path logs by relative volume. If one event shape represents a disproportionate share of a service’s logs, Tero treats the event as a hot-path candidate. Message content can support detection. Generic messages such asProcessing request or Handling item often indicate unconditional logging, but volume is the primary signal.