Separate status reports on a per service basis:

• e.g. status.edugain.org and status.eduroam.org.
• Something like status.ti.geant.org, does not make much sense. There is a reason why we brand each service service separately and we do not have {edutainment, eduroam, eduteams}.geant.org
• NiDi: While I assume this is the toplevel landig for a service specific status page, I assume "sub" services like e.g. edugain access check would be mabe visible as part of status.edugain, but not as seperate pages?

Align licenses for such monitoring

• For some services we already have/ are going to procure licenses. Can these be used?
• NiDi: Were these services evaluate in any way against requirements of all services in scope?

Use (commercial) as a service offering

• very much in favour of going to a commercial vendor and get this as a service, rather than develop/operate something ourselves

In incubator or without?

• For eduTeAMS: I would like to develop this directly in the eduTEAMS team with my operations team