Merge Component service and monitor
|Status:||Request For Comments||Start date:||05/05/2015|
|Assignee:||Portier Thomas||% Done:|
removing monitor component
I think that we could merge the service and monitor components.
It could work like that :
- Add a radio button in the definition of a service : Monitor (yes/no). It will do a getCapabilities on the service.
- Add global parameters in the service component to fix url of the monitor service, email to alert when a status service change, the frequency of the requests
- Add a Monitor menu entry to display results of the monitoring with a selection of service monitored and a period that will display a D3 graph includind response time and status changes
The servlet works great, we could just keep it as it is
#2 Updated by Mérour Xavier over 4 years ago
I am personnaly in favor of such changes (these are directions PSC had already discussed) BUT it needs more description and layouts proposals (wireframe for example).
Both functional impact and ergonomic impacts MUST be addressed.
What about current MONITOR entry in backend ?
What about other parameters (SLA, advanced requests such as GetMap..., etc...) ?