TRS Delta Monitoring Task (DMT) Troubleshooting
Authors: WilliamChatham Build basis: V7.0.2, V7.0.3 and V7.1.
The objective of page is to provide an overview of the TRS Delta Monitoring Task (DMT) and also include troubleshooting steps.
What is the Delta Monitoring Task (DMT):
The DMT purpose is to query for and processes three kinds of change (in this order)- Apply compensating actions.
- Process changes in durable log (eg user makes a change to a requirement).
- Container recovery.
- The DMT is executed every 2 seconds (non configurable).
- The DMT gives Administrators a way to determine how up to date TRS processing is.
- DMT can be monitored by Administrators in the Tracked Resource Set monoto0ring page which shows the Watermark (How up to date the TRS processing is) :
Watermark
In Log based we have a new concept of the "Watermark”- Watermark includes a pair of timestamps [t1, t2)
- Defines the “currency” of the TRS
- Everything before t2 in the DB is up-to-date in the TRS (*)
- TRS status shows the watermark.
- Its duration, and the lag.
Compensation actions:
Compensation actions result in changes in the changelog- Archive & restore - ExcludedContainers
- Baseline is excluded As archive/restore
- Historic baseline is created (since 7.1) – As restore
- Repair & purge – when a state has been modified (no ExcludedContainer)
- Applying compensation actions does not alter the watermark interval
- ExcludedContainer will be added and then removed when compensationfinished
- Unchanging watermark could be due to compensation actions
DMT Troubleshooting
TBDDMT Performance
TBDHow to determine what the DMT is processing:
TBDRelated topics: Deployment web home, Deployment web home
External links:
Additional contributors: TWikiUser, TWikiUser

Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.