= Service status guidelines =

'''Guidelines under construction! '''

This is a (draft) guideline for dealing with expected and unexpected downtime of A-services and other central/crucial CLARIN services.

== Monitoring ==
'''Be aware''' that important CLARIN services are monitored in various ways; primarily using [[SystemAdministration/Monitoring/Icinga|Icinga]] but there are also [http://uptimerobot.com/ Uptime Robot] and [https://www.statuscake.com/ StatusCake] that hook into a private Slack channel, thus notifying the CLARIN administrators. 

Live and historical !StatusCake data is available at [http://status.clarin.eu status.clarin.eu].

== Expected downtime report ==

Use the [https://goo.gl/forms/Mqzeu7Td0NXQ4UPP2 expected service downtime report form] to '''submit your expected downtime'''. The central development/admin team will then process the information into the [https://www.clarin.eu/status CLARIN services status page].

Don't forget to [mailto:sysops@clarin.eu notify the system administrators] when your service is back up!

== Unexpected downtime ==

{todo}

== On-site maintenance notification ==

It is a good practice to replace the content of your service page/front end/portal with a page showing a message indicating the current status and expected timeframe of the activities causing the downtime. However, if you do so, make sure to return a '''503 Service Unavailable''' response code so that automated status checker can recognise the current state of your service.

Also see this [https://moz.com/blog/how-to-handle-downtime-during-site-maintenance post on how to handle downtime during site maintenance].

== More information ==

* [[SystemAdministration/Monitoring/Icinga|Monitoring CLARIN infra using ​Icinga]]
* [https://www.clarin.eu/content/service-criteria A-service criteria]