Canonical: https://weaveos.com/glossary/white-box-monitoring

[Home](https://weaveos.com/)/[Glossary](https://weaveos.com/glossary)/[Reliability and observability](https://weaveos.com/glossary/category/reliability-observability)/White-box monitoring

[Reliability and observability](https://weaveos.com/glossary/category/reliability-observability)

# White-box monitoring

Also known as White-box monitoring

By WeavePublished September 10, 20261 min read

## Definition

White-box monitoring is monitoring based on internal measurements such as resource use, queues, errors, and latency.

On this page

1. [Definition](https://weaveos.com/glossary/white-box-monitoring#definition)
2. [What White-box monitoring shows](https://weaveos.com/glossary/white-box-monitoring#article-what-white-box-monitoring-shows)
3. [A concrete example](https://weaveos.com/glossary/white-box-monitoring#article-a-concrete-example)
4. [Limitations and tradeoffs](https://weaveos.com/glossary/white-box-monitoring#article-limitations-and-tradeoffs)
5. [How this relates to Weave](https://weaveos.com/glossary/white-box-monitoring#weave)
6. [Sources](https://weaveos.com/glossary/white-box-monitoring#sources)
7. [Related terms](https://weaveos.com/glossary/white-box-monitoring#related)

## What White-box monitoring shows

White-box monitoring is monitoring based on internal measurements such as resource use, queues, errors, and latency. It matters when a team can state the decision the evidence should support, the population being measured, and the time window in which the observation matters. That framing keeps a familiar label from becoming a dashboard tile with no operational meaning. The collection method and owner should be visible whenever the signal is used in a review.

## A concrete example

Queue depth and retry count rise before a public endpoint starts timing out. A useful workflow records relevant context, compares the observation with an appropriate baseline, and follows the evidence to the service or change that may explain it. The signal should start a question rather than close the investigation. Teams should also record what action follows a meaningful change and how the result will be checked.

## Limitations and tradeoffs

Internal health can coexist with a broken user journey or external dependency. Interpret white-box monitoring alongside related signals and explicit service objectives. Sampling, aggregation, clock behavior, retention, and access policy can all affect what an operator sees. When those details are missing, conclusions should remain provisional and a precise-looking value should not be presented as a complete account of user experience.

## How this relates to Weave

Weave can help teams connect engineering delivery evidence with white-box monitoring questions. It can provide context from code, reviews, releases, and ownership, while the direct white-box monitoring measurement should remain in the system that collects it. Treat relationships as investigation leads and verify them against service telemetry and user impact.

[Explore Engineering intelligence](https://weaveos.com/products/engineering-intelligence)

## Sources and further reading

1. [Primary documentation: White-box monitoring](https://sre.google/sre-book/monitoring/)

## Related terms

### [Observability](https://weaveos.com/glossary/observability)

[Understand observability, the role of logs, metrics, and traces, and why telemetry only helps when it answers useful questions.](https://weaveos.com/glossary/observability)

### [Distributed tracing](https://weaveos.com/glossary/distributed-tracing)

[How distributed tracing follows a request across services, what spans contain, and why trace context matters for debugging.](https://weaveos.com/glossary/distributed-tracing)

### [Trace context](https://weaveos.com/glossary/trace-context)

[What trace context carries between services, how propagation connects spans, and what breaks when context is lost.](https://weaveos.com/glossary/trace-context)
