From c83dc552b697e1e76c741dbe7a1b98f1677fed3f Mon Sep 17 00:00:00 2001
From: Ian McGinnis <67600557+ian-noaa@users.noreply.github.com>
Date: Fri, 13 Oct 2023 14:45:59 -0600
Subject: [PATCH] Add instructions on how to access the prod logs

---
 CONTRIBUTING.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 93296bc0..828d4103 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -99,3 +99,19 @@ pip3 install --user pre-commit
 The `pre-commit` script will check all of the files in your index with our
 linters and formatters and warn you if any of the files fail linting and
 formatting checks.
+
+
+## Checking production infrastructure
+
+The applications here are automatically deployed to an AWS account. If you need to check the logs in production you can do so by logging into the appropriate AWS console and then:
+
+For the ETL application:
+
+* Going to "Cloudwatch" -> "Log Groups". Logs are under the following log groups:
+	* `/aws/lambda/rtma-vis-netcdf-processor`
+	* `/aws/lambda/rtma-vis-nodd-processor`
+
+For the web app:
+
+* Connect via Session Manager to the `kubernetes-readonly-rtma-vis` EC2 instance
+* Use kubectl to read the logs directly (`kubectl logs unified-graphics-api...`)