> An RFTS enables fiber to be automatically tested from a central location. A central computer is used to control the operation of OTDR-like test components located at key points in the fiber network. The test components scan the fiber to locate problems. If a problem is found, its location is noted and the appropriate personnel are notified to begin the repair process.
There are a lot of more thing than just making sure the media is working. And you would be quite surprised (considering you are throwing Wiki links for a reflectometry) but the physical state of the line is the least important thing in making sure what something can communicate with something else. A sibling comment can provide a glimpse on how it can be done.
If I lose a link anywhere in the world then BGP reroutes within a second or so, and we get a notification in seconds or maybe minutes on slack depending on how busy slack is being.
If it's down for more than 15 minutes in country or 2 hours internationally it gets flagged for manual attention. Shorter outages are logged but only looked at monthly as part of the operational report process.
Now sure you can have two independent faults on the same day, but the reports are that they didn't know the backup line was down.
Meh, I knew people would just clutch to the monitoring ignoring everything else.
In your case you already have way more than monitoring. You have the infrastructure designed for resilience. You have that design implemented. You have the protocols to do if the things go north. You have automation to disregard minor events and to bring to the attention more serious things. You have way more than monitoring alone.
No?
Like, okay, monitoring reports what there is no link.
Now what? Somebody gets a hi vis vest, a hard hat and goes along the cable to investigate the reason?
There is nothing monitoring could help, especially if the cable was cut recent enough.