Page MenuHomePhabricator

Write the monitoring specification for Maps
Closed, ResolvedPublic

Description

We have an automated monitoring service that can check services every 60 seconds for their responses. A specification exposing the endpoints to be monitored needs to be written for the Maps service. It can be based on the spec.template.yaml file already present in the repository.

Event Timeline

mobrovac raised the priority of this task from to Needs Triage.
mobrovac updated the task description. (Show Details)
mobrovac added subscribers: Yurik, MaxSem, mobrovac.
Deskana moved this task from Needs triage to Maps on the Discovery-ARCHIVED board.
Deskana subscribed.

Does the testing setup depend on this service being behind restbase? If not, we can use it for testing that @Gehel was looking at. Adding this task as a blocker

Does the testing setup depend on this service being behind restbase?

No. As the description says, you need to create spec.yaml which is to contain a Swagger specification of the endpoints and x-amples stanzas for each that contain request/response pairs which will allow for automatic monitoring in production. You can look at the specs of Citoid, Mathoid or MobileApps to get an idea.

Change 292090 had a related patch set uploaded (by Yurik):
Add spec.yaml with basic tests

https://gerrit.wikimedia.org/r/292090

Change 292090 merged by Yurik:
Add spec.yaml with basic tests

https://gerrit.wikimedia.org/r/292090

This is deployed and working. Monitoring can be seen in Icinga.