Skip to content

ISO 8601 format on first and last load time for plan when connect to … - #50952

Open
tharun0064 wants to merge 1 commit into
open-telemetry:mainfrom
newrelic-forks:oracledbreceiver-iso-8601-firs-last-load-time
Open

ISO 8601 format on first and last load time for plan when connect to …#50952
tharun0064 wants to merge 1 commit into
open-telemetry:mainfrom
newrelic-forks:oracledbreceiver-iso-8601-firs-last-load-time

Conversation

@tharun0064

Copy link
Copy Markdown
Contributor

…CDB root

Description

When connected to CDB , V$SQL.FIRST_LOAD_TIME and LAST_LOAD_TIME are VARCHAR2 columns in Oracle's
native format (YYYY-MM-DD/HH24:MI:SS), not ISO 8601. The db.server.top_query
log event emitted these raw, while other timestamp attributes on the same
event (e.g. derived from SQL_EXEC_START) are already converted to ISO 8601
UTC. This fixes oracledb.plan.first_load and oracledb.plan.last_load to use
the same TO_CHAR(SYS_EXTRACT_UTC(FROM_TZ(...))) conversion, so all timestamp
attributes on the event are consistently formatted. Also updated the
metadata.yaml descriptions and regenerated documentation.md to match.

Link to tracking issue

Fixes
Fixes #50951

Testing

Documentation

Authorship

  • I, a human, wrote this pull request description myself.

@ebrdarSplunk ebrdarSplunk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tharun0064

Copy link
Copy Markdown
Contributor Author

@atoulme can you please review and merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[receiver/oracledb] first_load_time in db.server.top_query events is not formatted as ISO 8601

2 participants