feat(monitoring): add dns reporter

[kishore03109]

Problem

This is a first pr that is up to add some level of sane reporting. While scheduling is part of this feature, it is not within the scope of this pr. This pr only adds (currently dead code) logic to grab the domains that we own in isomer, and do a dns dig. This is meant to be verbose, and in the future alarms can be added based on the results of this.

This is not meant to replace monitoring, it is just meant to fine tune some blind spots that uptime robot currently has + some sane checker during incident response to show history of dns records for a site that we manage.

I am opting to log it directly in our backend to keep things simple. will add alarms + the scheduler in subsequent prs.

Solution

grab ALL domains from keycdn + amplify + redirection records + log dns records on them.

Breaking Changes

• [ ] Yes - this PR contains breaking changes
  • Details ...
• [X] No - this PR is backwards compatible with ALL of the following feature flags in this doc

Tests

in server.ts add: monitoringService.driver()

should see this in the logs:

Deploy Notes

New environment variables:

• KEYCDN_API_KEY : to get all the zones that we own in keycdn

• REDIRECTION_REPO_GITHUB_TOKEN: gh token to view redir repo

  • [ ] HAVE NOT added env var to 1PW + SSM script

  (fetch_ssm_parameters.sh)

New scripts:

• script : script details

New dependencies:

• dependency : dependency details

New dev dependencies:

• dependency : dependency details

[kishore03109]

• #1383
• #1376 👈
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kishore03109 and the rest of your teammates on Graphite

[kishore03109]

Merge activity

• Jun 27, 2:08 AM EDT: @kishore03109 started a stack merge that includes this pull request via Graphite.
• Jun 27, 2:08 AM EDT: @kishore03109 merged this pull request with Graphite.