[MGNLXAA-51] Improve logging to simplify issue tracking and to alert admins in case of low performance Created: 02/Nov/12  Updated: 08/Mar/13  Resolved: 05/Feb/13

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5, 1.3.6

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLXAA-60 XAReceiveFilter logs null user Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Each run of activation gets now transaction id printed in the logs to allow recombining related messages in case of multiple concurrent activations.
Alert is issued in the logs on public instance in case single activation of page in website takes more then 10 seconds.


Generated at Mon Feb 12 11:06:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.