[
https://issues.apache.org/jira/browse/CAUSEWAY-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated CAUSEWAY-4069:
------------------------------------------
Description:
Following the CAUSEWAY-3975 observation foundation work, establish consistent
telemetry conventions
Scope:
* Separate stable observation names from readable contextual span names.
* Replace instance-specific JPA observation names, including embedded
bookmarks and query descriptions, with bounded operation names and appropriate
attributes.
* Define whether username and tenancy attributes should be included by
default, omitted, or explicitly enabled.
* Review the fixed JPA duration threshold and how filtering affects trace
structure, particularly exported child spans whose parent was discarded.
* Document the resulting conventions and any changes affecting existing
telemetry queries or dashboards.
Acceptance criteria:
* Observation names and metadata follow a documented, consistent policy.
* Tests cover naming, metadata inclusion and filtering behavior.
* Both Boot-managed and Java-agent-owned tracing configurations remain
supported.
* Existing instrumentation coverage and error visibility are preserved.
This is a follow-up to CAUSEWAY-3975 and establishes the conventions for
subsequent semantic naming and tracing forward ports.
> Otel : standardize observation names, metadata and duration-filtering policy
> ----------------------------------------------------------------------------
>
> Key: CAUSEWAY-4069
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-4069
> Project: Causeway
> Issue Type: Improvement
> Components: Core
> Reporter: Daniel Keir Haywood
> Assignee: Daniel Keir Haywood
> Priority: Minor
> Fix For: 4.0.0
>
>
> Following the CAUSEWAY-3975 observation foundation work, establish consistent
> telemetry conventions
> Scope:
> * Separate stable observation names from readable contextual span names.
> * Replace instance-specific JPA observation names, including embedded
> bookmarks and query descriptions, with bounded operation names and
> appropriate attributes.
> * Define whether username and tenancy attributes should be included by
> default, omitted, or explicitly enabled.
> * Review the fixed JPA duration threshold and how filtering affects trace
> structure, particularly exported child spans whose parent was discarded.
> * Document the resulting conventions and any changes affecting existing
> telemetry queries or dashboards.
> Acceptance criteria:
> * Observation names and metadata follow a documented, consistent policy.
> * Tests cover naming, metadata inclusion and filtering behavior.
> * Both Boot-managed and Java-agent-owned tracing configurations remain
> supported.
> * Existing instrumentation coverage and error visibility are preserved.
> This is a follow-up to CAUSEWAY-3975 and establishes the conventions for
> subsequent semantic naming and tracing forward ports.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
