Description

None

How to test

None

How to document

None

Attachments

2

Activity

Alexey Palazhchenko 
April 20, 2020 at 9:41 AM

C W 
January 8, 2020 at 12:00 PM

that's fine, so long as all services that should be in the RUNNING state under normal operations are checked

Alexey Palazhchenko 
January 8, 2020 at 11:16 AM

Please rely only on:

  • response code is 200 = container is ready;

  • any other response code or no code at all = container is not ready.

Do not really on other response codes, any response body (including empty JSON), etc. Supporting many failure modes requires a disproportionate amount of effort to the benefits.

C W 
January 8, 2020 at 11:01 AM

we require v1/readyz to confirm that everything is ready, not just Prometheus. In particular, Grafana needs to be monitored as there is no clean way to check that we can interact with the API.

Also, you currently get an HTML 500 response by stopping pmm-managed, so adding that will presumably require NGINX adjustments to return a JSON 500 when requesting with Content-type: application/json

Alexey Palazhchenko 
July 30, 2019 at 10:57 AM

For to plan / prioritize future work.

Details

Assignee

Unassigned

Reporter

Tim Vaillancourt(Deactivated)

Priority

High

Components

Needs QA

Yes

Needs Doc

No

Fix versions

Story Points

2

Sprint

None

Smart Checklist Progress

0/1