Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourRed
titleDRAFT

Table of Contents

Overview

Voluntarily has various service endpoints Managing Access to open platforms and this page gives a high level overview on how these are set up.

...

Things missing here:

  • cloudflare setup

Monitoring and Metrics

Have a dashboard setup to view application and infrastructure usage data, telemetry.

High level Design

(in progress)..

Infrastructure

  • load Balancers

  • Fargate Service

  • CPU/Memory Usage

Current Setup:

Cloud Watch dashboard setup for ELB and ECS services used by vly. Enabled ‘container insights’ for ECS services. View sample dashboard: https://ap-southeast-2.console.aws.amazon.com/cloudwatch/home?region=ap-southeast-2#dashboards:name=vly-services;accountId=585172581592

ToDo: Team consensus and understanding on setup. Naming. Add further missing information, check existing setup, compare differences and fix what is needed.

Application

  • Application metrics

  • tracing?

  • Health end points

  • separate Test Suite/service deployed for regular(5 min interval?) app endpoint checks?

Current Setup:

Notifications

  • possibly start with slack channel notifications

  • aws infrastructure can utilise cloudwatch and SNS

Current Setup:

Cloud watch Alert → SNS Topic → Lambda function to push alert to Slack channel ‘#notifications’

ToDo:

  • Refire alert if it is not addressed

  • serverless setup for lambda function code, currently its just a quick demo

Logging

thoughts:

  • configure log levels based on env var so just update env var to DEBUG and get all logs

  • log rotation?

  • standardised log solution

Tracing

thoughts: (do we want this?)

  • standardised distributed trace solution?

  • i have previously worked with Jaeger-open tracing standard - OpenTracing standard