Actions
Feature #4540
closedensure there are counters indicating lchans entering and leaving the broken state (BORKEN)
Start date:
05/09/2020
Due date:
% Done:
100%
Spec Reference:
Description
currently the lchan summary shows currently broken lchans, but it would be good to have counters publishing per BTS how often a broken lchan occurs,
especially when some situations (late ACK) recover from the broken state, and the lchan summary no longer shows that anything was broken at any point.
Related issues
Updated by neels almost 4 years ago
- Related to Feature #4537: OsmoBSC needs strategies to recover broken lchans (lchan state BORKEN) added
Updated by neels almost 4 years ago
- Status changed from New to Resolved
- Assignee set to ipse
- % Done changed from 0 to 100
merged
Actions