Page MenuHomePhabricator

Investigate Monitoring Kask Availability via Integration Tests
Open, LowPublic8 Estimate Story Points

Description

Description
A potential use case for our Integration Test Framework is as a monitoring tool to support health checks on services. As an initial step we want to investigate whether or not the Integration Test Framework will be sufficient to provide Monitoring for instances of the Kask Service.

Requirements

  • Determine and document on the wiki the criteria for supporting monitoring
  • Evaluate use of Integration Test Framework for against criteria
  • Document results of evaluation on the wiki

Related Objects

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 15 2019, 9:37 PM
WDoranWMF triaged this task as Medium priority.Oct 15 2019, 9:37 PM
WDoranWMF lowered the priority of this task from Medium to Low.Oct 16 2019, 1:21 PM
WDoranWMF updated the task description. (Show Details)Oct 16 2019, 7:48 PM
WDoranWMF set the point value for this task to 8.Oct 16 2019, 7:54 PM
Clarakosi moved this task from Ready to Doing on the Core Platform Team Workboards (Green) board.

@Clarakosi The draft looks great! The comparison table is set up nicely, and the doc is easy to understand. Nice work!

@Clarakosi This is excellent. Can you move it to the section Decisions of Record, Architecture and Research on the CPT main page.

Are there next steps that can come out of this? I know one is for @Eevans to complete a test for Kask, it seems like we would want to form this into an initiative for future planning and that we might also want to shares this back with other services owners or the QA Engineering team.

Thanks for reviewing @apaskulin & @WDoranWMF! I moved the page to the section Decisions of Record, Architecture and Research on the CPT main

Are there next steps that can come out of this? I know one is for @Eevans to complete a test for Kask, it seems like we would want to form this into an initiative for future planning and that we might also want to shares this back with other services owners or the QA Engineering team.

+1. And I think the next steps may also include conversations with SRE