Skip to content

Running checks from multiple locations #145

@jeremych1000

Description

@jeremych1000

Hello! Stumbled upon this tool and it looks perfect for an uptime monitoring system that I'm building out. I have two quick questions.

  1. Running from multiple regions
  • I am planning to use checkup to monitor uptime of a service
  • I am planning to deploy checkup using AWS Lambdas in multiple regions to improve redundancy of the system
  • How does checkup recommend I go about this? Would I deploy multiple copies of the frontend, checkup, and db? Or use one main frontend + db in one region, and multiple checkup lambdas in other regions, all reporting back to the single main region db?
  • If one region, surely the response times will be vastly different depending on the region I'm pinging from - how does uptime differentiate between these?
  1. HA Checkup
  • There is a requirement to make this uptime monitoring solution a mission critical service, so high availability of the service needs to be built in
  • What happens if the storage mechanism is unavailable e.g. the postgres db is unavailable due to a cloud outage?
  • I don't see an option to have multiple storage backends defined, is it possible to do this? For example, store everything into postgres with a backup in S3, so in case postgres goes down we still have uptime metrics in S3?

Our high level planned architecture:

  • AWS Lambda for checkup checks
  • AWS Fargate for checkup frontend, fronted by a load balancer
  • AWS Aurora Postgres for checkup's DB

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions