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.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T137616 Epic: cultivating the Maps garden | |||
Resolved | Gehel | T135647 Configure monitoring / alerting of Postgresql / redis / ... cluster for maps | |||
Resolved | • mobrovac | T109021 Code review of Maps service | |||
Resolved | None | T111951 Write the monitoring specification for Maps |
Event Timeline
Comment Actions
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
Comment Actions
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.
Comment Actions
Change 292090 had a related patch set uploaded (by Yurik):
Add spec.yaml with basic tests