chore: log incoming message execution time #1414

MadsDue · 2024-12-09T09:30:13Z

Description

see title

Should the change be behind a feature flag?
Can the feature be meaningfully disabled or circumvented if there are issues (e.g., database-breaking changes)?
Has it been considered whether data is being delivered to the wrong actor?
Subsystem test executed (dev_002/dev_003) => https://github.com/Energinet-DataHub/dh3-environments/actions/runs/12251577051
Is there time to monitor state of the release to Production?
Reference to the task => https://app.zenhub.com/workspaces/mosaic-60a6105157304f00119be86e/issues/gh/energinet-datahub/team-mosaic/426

source/B2BApi/IncomingMessages/IncomingMessageReceiver.cs

chore: log incoming message execution time

e2380e9

MadsDue temporarily deployed to AzureAuth December 9, 2024 09:30 — with GitHub Actions Inactive

Merge branch 'main' into madu/log-incoming-message-execution-time

4432ece

MadsDue marked this pull request as ready for review December 10, 2024 07:23

MadsDue requested a review from a team as a code owner December 10, 2024 07:23

MadsDue requested a review from ebbeknudsen December 10, 2024 07:23

MadsDue temporarily deployed to AzureAuth December 10, 2024 07:23 — with GitHub Actions Inactive

MWO1024 approved these changes Dec 10, 2024

View reviewed changes

ebbeknudsen reviewed Dec 10, 2024

View reviewed changes

source/B2BApi/IncomingMessages/IncomingMessageReceiver.cs Show resolved Hide resolved

ebbeknudsen approved these changes Dec 10, 2024

View reviewed changes

MadsDue merged commit f52e219 into main Dec 10, 2024
47 checks passed

MadsDue deleted the madu/log-incoming-message-execution-time branch December 10, 2024 11:38