github.com/stakater/IngressMonitorController@v1.0.103/docs/updown-configuration.md (about) 1 # Updown Configuration 2 3 ## Note 4 5 | Caveats | Description | 6 |----------|-----------------------------------------------------| 7 | Email alert addresses | Currently, email addresses for check alerts can be assigned to a check, neither by its go client nor API. The only way to do it is by manually adding them on their website. A request has been added on updown's feature addition forum [link](https://updown.uservoice.com/forums/177972-general/suggestions/37334926-crud-for-setting-email-and-phone-alerts-for-a-chec) | 8 9 10 11 12 ## Compulsory Configuration 13 14 The following properties need to be configured for Updown, in addition to the general properties listed 15 in the [Configuration section of the README](../README.md#configuration): 16 17 18 | Key | Description | 19 |----------|--------------------------------------------------| 20 | apiKey | API key of an account | 21 22 23 ## Additional Configuration 24 25 Additional updown configurations can be added to each ingress object using annotations, current supported annotations are: 26 27 | Annotations | Description | 28 |----------------------------------------------------------|--------------------------------------------------| 29 | updown.monitor.stakater.com/enable | Set to "false" to disable checks | 30 | updown.monitor.stakater.com/period | The pingdom check interval in seconds, it accepts `only` these values: 15, 30, 60, 120, 300, 600, 1800, 3600 | 31 | updown.monitor.stakater.com/enable | Check be enabled or not ("true" or "false") | 32 | updown.monitor.stakater.com/publish-page | Status page be public or not ("true" or "false")| 33 | updown.monitor.stakater.com/request-headers | Custom updown request headers (e.g. {"Accept"="application/json"}) |