End targets should be monitored with respect to the availability and the status should be visible to the portal user and/or admin user.
Note: targets are visible today already. Target status is pre-defined, but not used/visible yet. We need to decide on whether we want to keep different kinds of "status" in future: provisioning status and availability status?
Future ideas (not in focus of this enhancement request)
we could think about sending emails to the admin(s) in case a target becomes unavailable.
Action Mailer is integral part of Rails v4.2 (as it is used in this project already), see here.
Monitoring of Apache Camel backend independed of end targets
Note: Apache Camel backend is not visible in the web portal at all. The model would have to be changed.
Note that different end targets are accessed via different interfaces:
OSV
SOAP/XML: here, we could "ping" with a GetVersion request
SSH/SFTP
as sysad user
as srx user
UC
SPML: there seems to be no get version request. We need to use another get request, e.g. spml_communicationsystem_search_all_request.xml (probably better than search user request, since the answer may be very large)
Following features:
Future ideas (not in focus of this enhancement request)
Note that different end targets are accessed via different interfaces: