# Observability Design §37. What is measured, and what must never appear in a measurement. ## What is emitted by default Nothing JPA-specific. No composition constructs a `MeterRegistry`-backed observation for the platform, and `SpringTransaction` records no transaction metric. The `jpa.transaction.*` meters this page used to list (`duration`, `rollback`, `timeout`, `completion.unknown`) were produced by `JpaTransactionObservation`, which nothing constructed; it was removed on 2026-09-25 (`docs/capability-status.md`). Transaction outcomes are visible through the shared persistence error codes and the application's own metrics, not through a JPA meter. ## Query metrics — only when the caller asks `jpa.query.duration` and `jpa.query.rows` are recorded by `MicrometerQueryObservation`, and only when a service passes it to a library executor that accepts a `QueryObservation` (`JpaStreamExecutor`, `HibernateBulkDmlExecutor`). The default is `NoopQueryObservation`. Rows are measured as well as duration because a query that issues one statement and hydrates twenty thousand rows is fast per statement and catastrophic per request — a duration metric alone reports it as merely slow. ## Bounded tags, always Every meter `MicrometerQueryObservation` records carries exactly five tags: persistence unit, operation, query, outcome, failure category (`JpaMetricTags`). All five are registered identifiers, validated by `LowCardinality` at construction rather than at the registry — so an unbounded value fails where it was introduced instead of surviving until a dashboard stops loading. Never a tag: entity id, tenant id, SQL parameter, exception message, JDBC URL. Each is unbounded, so each creates a time series per row or per failure; several are also the data the platform keeps out of logs, which a metrics backend would store just as durably and export just as widely. ## Query names in SQL `JpaRepositoryFragmentSupport` sets the registered query name as the `org.hibernate.comment` hint; Hibernate writes it into the SQL only when `hibernate.use_sql_comments=true`. The alternative is `NamedStatementInspector`, which prefixes a statement with the query name bound by `JpaStreamExecutor`, `JpaKeysetQuerySupport` or `JpaRepositoryFragmentSupport.observing(..)`. Neither is on by default: a deployment enables the inspector with `spring.jpa.properties.hibernate.session_factory.statement_inspector=dev.caskeleton.adapter.outbound.persistence.hibernate.NamedStatementInspector`. The comment then travels into `pg_stat_activity`, `auto_explain`, and the slow-query log. Without it, "which endpoint issues this query" is answered by grepping the codebase for fragments of SQL. ## Diagnostics `SqlDiagnosticRedactor.redact(sql)` removes string literals, numbers, and anything email-shaped. It is a utility for code that is about to log SQL; nothing in the platform logs SQL through it. Redaction is blunt on purpose: preserving "harmless" values would require knowing which columns hold personal data. ## The actuator endpoint `jpaplatform` reports database major version, provider version, schema version, OSIV state, runtime role verification, and capability levels. It reports no JDBC URL, no username, no SQL, and no entity catalog — an actuator endpoint is reachable by anyone who reaches the management port, and each of those would be a free reconnaissance answer. It is read-only: an endpoint that could trigger a migration or a repair would be an admin capability exposed over HTTP.