cds-snc / notification-planning-core

Project planning for GC Notify Core Team
0 stars 0 forks source link

Document NewRelic Lambda integration and clean up API keys #99

Open jimleroyer opened 1 year ago

jimleroyer commented 1 year ago

Description

As an ops lead, I want to know how the lambda reporting integration was done in between NewRelic and AWS, So that I can debug accordingly if things get broken but also recreate in for a new environment.

WHY are we building?

To know what we do. To recreate similar environments.

WHAT are we building?

Documentation and cleaning up the API keys that are not used by this integration.

VALUE created by our solution

To recreate environment properly and clean house.

Acceptance Criteria

QA Steps

Additional information

The integration was done within the context of this task, where links are provided on the installation. The newrelic-lambda-cli was used and we should be able to reinstall easily if necessary.

sastels commented 1 year ago

Api keys: https://one.newrelic.com/admin-portal/api-keys/home?duration=1800000&state=067e2c8f-0882-afb9-197c-642ae6dd6456

New relic lambda integration?? https://ca-central-1.console.aws.amazon.com/lambda/home?region=ca-central-1#/functions/newrelic-log-ingestion?tab=configure

This issue might be relevant? https://github.com/cds-snc/notification-planning/issues/238

We can see stats on api-lambda, heartbeat, ses_receiving_emails, ses_to_sqs_email_callbacks here https://one.newrelic.com/infra/aws?account=2691974&duration=3600000&state=6efb9d87-ae4f-2622-8cb2-9f5c300e8ecc

Some documentation https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/