@hklai commented on Mon Oct 09 2017

Context: production readiness proposal and plan

The feature “Mixer monitoring” is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.

This issue is initially assigned to the working group leads.

Recommendations:

• Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
• If you expect the test plan is complex and controversial, consider having it formally reviewed.
• State an ETA in the issue, and assign this to a developer who will execute the test plan.
• Execute the test plan as the highest priority for 0.3.
• For any bug or defect identified by the new test cases, file a new issue and link it from this one.
  Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact istio-production-quality@googlegroups.com as soon as possible. We will also periodically ping the issue for update.

@mandarjog commented on Thu Dec 14 2017

Plan

1. Review that grpc, dispatch, resolver and adapter level metrics are adequate.
2. Write tests to verify that correct metrics are produced.

@douglas-reid assigning to you.