Summary of the problem (If there are multiple problems or use cases, prioritize them)
This MVP would be first step in improving service landing page.
Main goal is to introduce more actionable troubleshooting workflows and leverage more data points about the service performance.

User stories

• As service owner, I would like to see key details about my service like version, framework, runtime, platform or cloud to validate current state of the service.
• As App Ops, I need to have visibility into timeline of anomalies, alerts and change events correlated to the service KPIs to better identify and isolate issues.
• As App Ops, I need to understand impact of downstream services and backends onto the service in question in order to troubleshoot isolate problem root cause and increase MTTR.
• As App Ops, I need to have visibility into how service is performing across its infrastructure in order to isolate issues related to specific instances, geos, deployments, etc.

List known (technical) restrictions and requirements

1. Able to scale to different time-frames from 15 minutes to multiple weeks.
2. Scalable to list multiple dependencies (10+).
3. Scalable to list multiple service instances (10 to 100s).

If in doubt, don’t hesitate to reach out to the #observability-design Slack channel.

Design issue: https://www.figma.com/proto/WkQsIVDmiYuHkvcXbzYBtg/268-%2F-Service-landing-page?node-id=513%3A2599&viewport=2040%2C-1389%2C0.5&scaling=min-zoom