Repository: redhat-developer/red-hat-developers-documentation-rhdh
Pull request #1089: RHIDP-6507 - modularize _Monitoring and logging with AWS
Author: login: themr0c
Labels: name: Ready to merge  :guard:
name: Peer review done :blue_book:
Created: 2025-04-22T12:31:57Z | Merged: 2025-04-30T07:14:23Z

RHIDP-6507 - modularize _Monitoring and logging with AWS_

**Version(s):** 1.6

**Issue:** https://issues.redhat.com/browse/RHIDP-6507

**Preview:** https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1089/monitoring-and-logging/#proc-rhdh-monitoring-logging-aws_assembly-rhdh-observability




Diff:
diff --git a/assemblies/assembly-logging-with-amazon-cloudwatch.adoc b/assemblies/assembly-logging-with-amazon-cloudwatch.adoc
new file mode 100644
index 00000000000..3d3c7b90573
--- /dev/null
+++ b/assemblies/assembly-logging-with-amazon-cloudwatch.adoc
@@ -0,0 +1,16 @@
+[id="assembly-logging-with-amazon-cloudwatch_{context}"]
+= Logging with Amazon CloudWatch
+
+Logging within the {product} relies on the link:https://github.com/winstonjs/winston[Winston library].
+The default logging level is `info`.
+To have more detailed logs, set the `LOG_LEVEL` environment variable to `debug` in your {product} instance.
+
+
+include::modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc[leveloffset=+1]
+
diff --git a/assemblies/assembly-monitoring-and-logging-with-aws.adoc b/assemblies/assembly-monitoring-and-logging-with-aws.adoc
new file mode 100644
index 00000000000..5e90e14d8f6
--- /dev/null
+++ b/assemblies/assembly-monitoring-and-logging-with-aws.adoc
@@ -0,0 +1,11 @@
+[id="assembly-monitoring-and-logging-with-aws_{context}"]
+= Monitoring and logging {product} on {aws-brand-name} ({aws-short})
+
+You can configure {product} to use Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging.
+This is convenient when hosting {product-short} on {aws-brand-name} ({aws-short}) infrastructure.
+
+include::assembly-monitoring-with-amazon-prometheus.adoc[leveloffset=+1]
+
+
+include::assembly-logging-with-amazon-cloudwatch.adoc[leveloffset=+1]
+
diff --git a/assemblies/assembly-monitoring-with-amazon-prometheus.adoc b/assemblies/assembly-monitoring-with-amazon-prometheus.adoc
new file mode 100644
index 00000000000..5f31e876df6
--- /dev/null
+++ b/assemblies/assembly-monitoring-with-amazon-prometheus.adoc
@@ -0,0 +1,22 @@
+[id="assembly-monitoring-with-amazon-prometheus_{context}"]
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+Amazon Prometheus extracts data from pods that have specific pod annotations.
+
+== Prerequisites
+
+* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to import the {product-short} metrics].
+* You ingested Prometheus metrics into the created workspace.
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]
+
+
+
+
diff --git a/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc b/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc
new file mode 100644
index 00000000000..14ba807798e
--- /dev/null
+++ b/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc
@@ -0,0 +1,34 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Helm chart
+
+To enable logging to Amazon Prometheus, you can configure the required pod annotations by using the {product} Helm chart.
+
+.Procedure
+* To annotate the backstage pod for monitoring, update your `values.yaml` file as follows:
++
+[source,yaml]
+----
+upstream:
+  backstage:
+    # --- TRUNCATED ---
+    podAnnotations:
+      prometheus.io/scrape: 'true'
+      prometheus.io/path: '/metrics'
+      prometheus.io/port: '9464'
+      prometheus.io/scheme: 'http'
+----
+
+.Verification
+To verify if the scraping works:
+
+. Use `kubectl` to port-forward the Prometheus console to your local machine as follows:
++
+[source,bash]
+----
+kubectl --namespace=prometheus port-forward deploy/prometheus-server 9090
+----
+
+. Open your web browser and navigate to `pass:c[http://localhost:9090]` to access the Prometheus console.
+
+. Monitor relevant metrics, such as `process_cpu_user_seconds_total`.
+
diff --git a/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc b/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
new file mode 100644
index 00000000000..2caaeb535b0
--- /dev/null
+++ b/modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
@@ -0,0 +1,51 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+To enable logging to Amazon Prometheus, you can configure the required pod annotations by using the {product} Operator.
+
+.Procedure
+. As an administrator of the {product} Operator, edit the default configuration to add Prometheus annotations as follows:
++
+----
+# Update OPERATOR_NS accordingly
+$ OPERATOR_NS=rhdh-operator
+$ kubectl edit configmap backstage-default-config -n "${OPERATOR_NS}"
+----
+
+. Find the `deployment.yaml` key in the config map and add the annotations to the `spec.template.metadata.annotations` field as follows:
++
+[source,yaml]
+----
+deployment.yaml: |-
+  apiVersion: apps/v1
+  kind: Deployment
+  # --- truncated ---
+  spec:
+    template:
+      # --- truncated ---
+      metadata:
+        labels:
+         rhdh.redhat.com/app:  # placeholder for 'backstage-<cr-name>'
+        # --- truncated ---
+        annotations:
+          prometheus.io/scrape: 'true'
+          prometheus.io/path: '/metrics'
+          prometheus.io/port: '9464'
+          prometheus.io/scheme: 'http'
+  # --- truncated ---
+----
+
+. Save your changes.
+
+.Verification
+To verify if the scraping works:
+
+. Use `kubectl` to port-forward the Prometheus console to your local machine as follows:
++
+----
+$ kubectl --namespace=prometheus port-forward deploy/prometheus-server 9090
+----
+
+. Open your web browser and navigate to `pass:c[http://localhost:9090]` to access the Prometheus console.
+. Monitor relevant metrics, such as `process_cpu_user_seconds_total`.
+
diff --git a/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc b/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc
new file mode 100644
index 00000000000..40349b7a1b5
--- /dev/null
+++ b/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc
@@ -0,0 +1,17 @@
+[id="configuring-the-application-log-level-by-using-the-helm-chart_{context}"]
+= Configuring the application log level by using the {product} Helm chart
+
+You can configure the application log level by using the {product} Helm chart.
+
+.Procedure
+* Modify the logging level by adding the environment variable `LOG_LEVEL` to your Helm chart `values.yaml` file:
++
+[source,yaml]
+----
+upstream:
+  backstage:
+    # --- Truncated ---
+    extraEnvVars:
+      - name: LOG_LEVEL
+        value: debug
+----
diff --git a/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-operator.adoc b/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-operator.adoc
new file mode 100644
index 00000000000..7a6ea6a5319
--- /dev/null
+++ b/modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-operator.adoc
@@ -0,0 +1,18 @@
+[id="configuring-the-application-log-level-by-using-the-operator_{context}"]
+= Configuring the application log level by using the {product} Operator
+
+You can configure the application log level by using the {product} Operator.
+
+.Procedure
+* Modify the logging level by including the environment variable `LOG_LEVEL` in your custom resource as follows:
++
+[source,yaml]
+----
+spec:
+  # Other fields omitted
+  application:
+    extraEnvs:
+      envs:
+        - name: LOG_LEVEL
+          value: debug
+----
diff --git a/modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc b/modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
new file mode 100644
index 00000000000..e1eb6c37ae6
--- /dev/null
+++ b/modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
@@ -0,0 +1,25 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
+
+* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+[subs="+quotes"]
+----
+/aws/containerinsights/_<cluster_name>_/application
+----
+
+.Procedure
+* To retrieve logs from the {product-short} instance, run a query such as:
++
+[source,sql]
+----
+fields @timestamp, @message, kubernetes.container_name
+| filter kubernetes.container_name in ["install-dynamic-plugins", "backstage-backend"]
+----
diff --git a/modules/observe/proc-rhdh-monitoring-logging-aws.adoc b/modules/observe/proc-rhdh-monitoring-logging-aws.adoc
deleted file mode 100644
index 822688a08ea..00000000000
--- a/modules/observe/proc-rhdh-monitoring-logging-aws.adoc
+++ /dev/null
@@ -1,149 +0,0 @@
-[id='proc-rhdh-monitoring-logging-aws_{context}']
-= Monitoring and logging with Amazon Web Services (AWS) in {product}
-
-In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can ensure the reliability, scalability, and compliance of your {product-short} application hosted on AWS infrastructure. 
-
-This integration enables you to oversee, diagnose, and refine your applications in the Red Hat ecosystem, leading to an improved development and operational journey.
-
-== Monitoring with Amazon Prometheus
-
-{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
-
-To monitor {product-short} using https://aws.amazon.com/prometheus/[Amazon Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
-
-After ingesting Prometheus metrics into the created workspace, you can configure the metrics scraping to extract data from pods based on specific pod annotations.
-
-=== Configuring annotations for monitoring
-
-You can configure the annotations for monitoring in both Helm deployment and Operator-backed deployment.
-
-Helm deployment::
-+
---
-To annotate the backstage pod for monitoring, update your `values.yaml` file as follows:
-
-[source,yaml]
-----
-upstream:
-  backstage:
-    # --- TRUNCATED ---
-    podAnnotations:
-      prometheus.io/scrape: 'true'
-      prometheus.io/path: '/metrics'
-      prometheus.io/port: '9464'
-      prometheus.io/scheme: 'http'
-----
---
-
-Operator-backed deployment::
-+
---
-.Procedure
-
-. As an administrator of the operator, edit the default configuration to add Prometheus annotations as follows:
-+
-[source,bash]
-----
-# Update OPERATOR_NS accordingly
-OPERATOR_NS=rhdh-operator
-kubectl edit configmap backstage-default-config -n "${OPERATOR_NS}"
-----
-
-. Find the `deployment.yaml` key in the ConfigMap and add the annotations to the `spec.template.metadata.annotations` field as follows:
-+
-[source,yaml]
-----
-deployment.yaml: |-
-  apiVersion: apps/v1
-  kind: Deployment
-  # --- truncated ---
-  spec:
-    template:
-      # --- truncated ---
-      metadata:
-        labels:
-         rhdh.redhat.com/app:  # placeholder for 'backstage-<cr-name>'
-        # --- truncated ---
-        annotations:
-          prometheus.io/scrape: 'true'
-          prometheus.io/path: '/metrics'
-          prometheus.io/port: '9464'
-          prometheus.io/scheme: 'http'
-  # --- truncated ---
-----
-
-. Save your changes.
---
-
-.Verification
-
-To verify if the scraping works:
-
-. Use `kubectl` to port-forward the Prometheus console to your local machine as follows:
-+
-[source,bash]
-----
-kubectl --namespace=prometheus port-forward deploy/prometheus-server 9090
-----
-
-. Open your web browser and navigate to `pass:c[http://localhost:9090]` to access the Prometheus console.
-. Monitor relevant metrics, such as `process_cpu_user_seconds_total`.
-
-== Logging with Amazon CloudWatch logs
-
-Logging within the {product} relies on the https://github.com/winstonjs/winston[winston library]. By default, logs at the debug level are not recorded. To activate debug logs, you must set the environment variable `LOG_LEVEL` to debug in your {product} instance.
-
-=== Configuring the application log level
-
-You can configure the application log level in both Helm deployment and Operator-backed deployment.
-
-Helm deployment::
-+
---
-To update the logging level, add the environment variable `LOG_LEVEL` to your Helm chart's `values.yaml` file:
-
-[source,yaml]
-----
-upstream:
-  backstage:
-    # --- Truncated ---
-    extraEnvVars:
-      - name: LOG_LEVEL
-        value: debug
-----
---
-
-Operator-backed deployment::
-+
---
-You can modify the logging level by including the environment variable `LOG_LEVEL` in your custom resource as follows:
-
-[source,yaml]
-----
-spec:
-  # Other fields omitted
-  application:
-    extraEnvs:
-      envs:
-        - name: LOG_LEVEL
-          value: debug
-----
---
-
-=== Retrieving logs from Amazon CloudWatch
-
-The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS. For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
-
-To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster. Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
-
-CloudWatch names the log group where all container logs are consolidated in the following manner:
-
-`/aws/containerinsights/<ClusterName>/application`
-
-Following is an example query to retrieve logs from the Developer Hub instance:
-
-[source,sql]
-----
-fields @timestamp, @message, kubernetes.container_name
-| filter kubernetes.container_name in ["install-dynamic-plugins", "backstage-backend"]
-----
diff --git a/titles/monitoring-and-logging/master.adoc b/titles/monitoring-and-logging/master.adoc
index 9954c0ebf44..ffb370749d2 100644
--- a/titles/monitoring-and-logging/master.adoc
+++ b/titles/monitoring-and-logging/master.adoc
@@ -11,7 +11,7 @@ include::artifacts/attributes.adoc[]
 include::assemblies/assembly-rhdh-observability.adoc[leveloffset=+1]
 
 //AWS
-include::modules/observe/proc-rhdh-monitoring-logging-aws.adoc[leveloffset=+1]
+include::assemblies/assembly-monitoring-and-logging-with-aws.adoc[leveloffset=+1]
 
 //AKS
 include::assemblies/assembly-monitoring-and-logging-aks.adoc[leveloffset=+1]


Reviews:
user: login: pabel-rh
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-28T11:15:39Z
user: login: linfraze
body: I agree with @pabel-rh comments and suggestions. I added a few more. One important one is to reframe the language in a couple of places so that it does not read as if we are promising any outcomes, as this could have legal implications. 
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-28T18:53:57Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:39:18Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:40:23Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:40:52Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:41:28Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:52:49Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:55:25Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:56:03Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T12:57:47Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T13:03:26Z
user: login: linfraze
body: Looking good. Consider the following: 
- Looks like a few attributes were missed
- Looks like we format some URLs with `link:` but not all
- CloudWatch Container Insights branding
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T13:44:50Z
user: login: pabel-rh
state: APPROVED
author_association: MEMBER
submitted_at: 2025-04-29T14:01:26Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:08:29Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:09:47Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:10:31Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:11:18Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:12:19Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:13:07Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:13:55Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:26:51Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:57:18Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T14:58:06Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:00:27Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:02:29Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:07:27Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:18:51Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:20:26Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:20:49Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:29:21Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:29:50Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:33:08Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:36:51Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:40:07Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:41:55Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:43:27Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:44:17Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:45:06Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:46:03Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:46:28Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:47:09Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:47:49Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:48:19Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T15:49:09Z
user: login: linfraze
body: A couple more comments
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-29T20:52:35Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-30T06:23:47Z
user: login: themr0c
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-30T07:12:59Z

Review comments:
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: pabel-rh
body: Should there be a "link:" after see and before the link??
created_at: 2025-04-28T11:11:39Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
+
+To monitor {product-short} using https://aws.amazon.com/prometheus/[Amazon Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: pabel-rh
body: Should there be a "link:" after see and before the link??
And should it be "Amazon-managed"?
created_at: 2025-04-28T11:12:12Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,53 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the operator, edit the default configuration to add Prometheus annotations as follows:
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: pabel-rh
body: Should we say "Operator" with the uppercase O?
created_at: 2025-04-28T11:12:59Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,16 @@
+= Configuring the application log level
+
+You can configure the application log level by using the {product} Helm chart.
+
+.Procedure
+* Modify the logging level by adding the environment variable `LOG_LEVEL` to your Helm chart's `values.yaml` file:
path: modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc
user: login: pabel-rh
body: ```suggestion
* Modify the logging level by adding the environment variable `LOG_LEVEL` to your Helm chart `values.yaml` file:
```
https://www.ibm.com/docs/en/ibm-style?topic=grammar-possessives
created_at: 2025-04-28T11:14:51Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can ensure the reliability, scalability, and compliance of your {product-short} application hosted on AWS infrastructure.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: linfraze
body: We have attributes for partner names

> Amazon Web Services (AWS)
created_at: 2025-04-28T18:40:36Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can ensure the reliability, scalability, and compliance of your {product-short} application hosted on AWS infrastructure.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: linfraze
body: We need to be mindful of our language for legal reasons and be careful not to promise anything in prod docs 
```suggestion
In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can help meet the reliability, scalability, and compliance needs of your {product-short} application hosted on AWS infrastructure.
```
created_at: 2025-04-28T18:44:42Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can ensure the reliability, scalability, and compliance of your {product-short} application hosted on AWS infrastructure.
+
+This integration enables you to oversee, diagnose, and refine your applications in the Red Hat ecosystem, leading to an improved development and operational journey.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: linfraze
body: CCS strives to use more customer-centric language and avoid product-centric language. In general, "enables you" or "allows you" tends to be product-centric. To make this more user-centric, focus on what the user can do with the product vs. what the product can do. 
created_at: 2025-04-28T18:48:04Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can ensure the reliability, scalability, and compliance of your {product-short} application hosted on AWS infrastructure.
+
+This integration enables you to oversee, diagnose, and refine your applications in the Red Hat ecosystem, leading to an improved development and operational journey.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: linfraze
body: Again, be careful not to "promise" certain outcomes in the prod docs. 
created_at: 2025-04-28T18:49:33Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,53 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the operator, edit the default configuration to add Prometheus annotations as follows:
++
+[source]
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: linfraze
body: Is this yaml, if so consider using the [source] tag to apply yaml highlighting
created_at: 2025-04-28T18:51:14Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
```
created_at: 2025-04-29T12:39:17Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
+
+To monitor {product-short} using https://aws.amazon.com/prometheus/[Amazon Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
To monitor {product-short} using https://aws.amazon.com/prometheus/[Amazon-managed Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
```
created_at: 2025-04-29T12:40:23Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,53 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the operator, edit the default configuration to add Prometheus annotations as follows:
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
. As an administrator of the {product} Operator, edit the default configuration to add Prometheus annotations as follows:
```
created_at: 2025-04-29T12:40:51Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,53 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the operator, edit the default configuration to add Prometheus annotations as follows:
++
+[source]
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
```
created_at: 2025-04-29T12:41:28Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+In the {product}, monitoring and logging are facilitated through Amazon Web Services (AWS) integration. With features like Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging, you can help meet the reliability, scalability, and compliance needs of your {product-short} application hosted on AWS infrastructure.
+
+This integration enables you to oversee, diagnose, and refine your applications in the Red Hat ecosystem, leading to an improved development and operational journey.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: themr0c
body: ```suggestion
You can configure {product} to use Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging.
This is convenient when {product-short} is hosted on {aws-brand-name} ({aws-short}) infrastructure.
```
created_at: 2025-04-29T12:52:49Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Logging with Amazon CloudWatch logs
+
+Logging within the {product} relies on the https://github.com/winstonjs/winston[winston library]. By default, logs at the debug level are not recorded. To activate debug logs, you must set the environment variable `LOG_LEVEL` to debug in your {product} instance.
path: assemblies/assembly-logging-with-amazon-cloudwatch-logs.adoc
user: login: themr0c
body: ```suggestion
Logging within the {product} relies on the link:https://github.com/winstonjs/winston[Winston library]. By default, logs at the debug level are not recorded. To activate debug logs, you must set the environment variable `LOG_LEVEL` to debug in your {product} instance.
```
created_at: 2025-04-29T12:55:25Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,11 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
+
+You can configure {product} to use Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging.
+This is convenient when {product-short} is hosted on {aws-brand-name} ({aws-short}) infrastructure.
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: themr0c
body: ```suggestion
This is convenient when hosting {product-short} on {aws-brand-name} ({aws-short}) infrastructure.
```
created_at: 2025-04-29T12:56:03Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for EKS clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
```
created_at: 2025-04-29T12:57:46Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Logging with Amazon CloudWatch logs
+
+Logging within the {product} relies on the link:https://github.com/winstonjs/winston[Winston library]. By default, logs at the debug level are not recorded. To activate debug logs, you must set the environment variable `LOG_LEVEL` to debug in your {product} instance.
path: assemblies/assembly-logging-with-amazon-cloudwatch-logs.adoc
user: login: themr0c
body: ```suggestion
Logging within the {product} relies on the link:https://github.com/winstonjs/winston[Winston library].
The default logging level is `info`.
To have more detailed logs, set the environment variable `LOG_LEVEL` to `debug` in your {product} instance.
```
created_at: 2025-04-29T13:03:26Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
+
+To monitor {product-short} using https://aws.amazon.com/prometheus/[Amazon-managed Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: linfraze
body: ```suggestion
To monitor {product-short} using link:https://aws.amazon.com/prometheus/[Amazon-managed Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
```

We need `link:` before all links, right? I see that you added it in a few other places.
created_at: 2025-04-29T13:23:34Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: Consider using the attribute for Amazon EKS
created_at: 2025-04-29T13:28:31Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: ```suggestion
* CloudWatch Container Insights is used to capture logs and metrics for Amazon EKS.
```
Consider adding the Amazon or EKS attribute in front of CloudWatch for proper branding. 

CloudWatch Container Insights ends with an "s" but it is a single tool, therefore, it is correct to use "is" instead of "are". Also, AWS docs doesn't usually use "The" in front, so I removed it to align with their branding. 
created_at: 2025-04-29T13:31:11Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: ```suggestion
* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
```
created_at: 2025-04-29T13:35:46Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: Also consider replacing EKS with attribute
created_at: 2025-04-29T13:36:07Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+----
+/aws/containerinsights/<ClusterName>/application
+----
+
+.Procedure
+* Following is an example query to retrieve logs from the Developer Hub instance:
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: Replace Developer Hub with attribute
created_at: 2025-04-29T13:36:31Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+----
+/aws/containerinsights/<ClusterName>/application
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: ```suggestion
/aws/containerinsights/_<ClusterName>_/application
```
To italicize the variable per CCS guidelines
created_at: 2025-04-29T13:40:41Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+----
+/aws/containerinsights/<ClusterName>/application
+----
+
+.Procedure
+* Following is an example query to retrieve logs from the Developer Hub instance:
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
* Following is an example query to retrieve logs from the {product-short} instance:
```
created_at: 2025-04-29T14:08:29Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
```
created_at: 2025-04-29T14:09:47Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the {product} Operator, edit the default configuration to add Prometheus annotations as follows:
++
+----
+# Update OPERATOR_NS accordingly
+$ OPERATOR_NS=rhdh-operator
+$ kubectl edit configmap backstage-default-config -n "${OPERATOR_NS}"
+----
+
+. Find the `deployment.yaml` key in the ConfigMap and add the annotations to the `spec.template.metadata.annotations` field as follows:
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
. Find the `deployment.yaml` key in the config map and add the annotations to the `spec.template.metadata.annotations` field as follows:
```
created_at: 2025-04-29T14:10:30Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for Amazon EKS.
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
```
created_at: 2025-04-29T14:11:18Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* The CloudWatch Container Insights are used to capture logs and metrics for Amazon EKS.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for Amazon EKS] documentation.
+
+* To capture the logs and metrics, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+----
+/aws/containerinsights/<ClusterName>/application
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ack. Plus enable substitutions, then.
created_at: 2025-04-29T14:12:18Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,24 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
+
+* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
+
[subs="+quotes"]
```
created_at: 2025-04-29T14:13:06Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,25 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
+
+* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+[subs="+quotes"]
+----
+/aws/containerinsights/_<ClusterName>_/application
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
/aws/containerinsights/_<cluster_name>_/application
```
created_at: 2025-04-29T14:13:55Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,13 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. For more information about enabling or deploying Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
+
+To monitor {product-short} using link:https://aws.amazon.com/prometheus/[Amazon-managed Prometheus], you need to create an Amazon managed service for the Prometheus workspace and configure the ingestion of the Developer Hub Prometheus metrics. For more information, see link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[Create a workspace] and link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[Ingest Prometheus metrics to the workspace] sections in the Amazon documentation.
+
+After ingesting Prometheus metrics into the created workspace, you can configure the metrics scraping to extract data from pods based on specific pod annotations.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
{product} provides Prometheus metrics related to the running application. 


.Prerequisites
* You configured Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
* After ingesting Prometheus metrics into the created workspace, you can configure the metrics scraping to extract data from pods based on specific pod annotations.
```
created_at: 2025-04-29T14:26:51Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,16 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. 
+
+
+.Prerequisites
+* You configured Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
+* After ingesting Prometheus metrics into the created workspace, you can configure the metrics scraping to extract data from pods based on specific pod annotations.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
* You ingested Prometheus metrics into the created workspace.

.Next steps

* You can configure the metrics scraping to extract data from pods based on specific pod annotations.
```
created_at: 2025-04-29T14:57:17Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
+
+.Procedure
+. As an administrator of the {product} Operator, edit the default configuration to add Prometheus annotations as follows:
++
+----
+# Update OPERATOR_NS accordingly
+$ OPERATOR_NS=rhdh-operator
+$ kubectl edit configmap backstage-default-config -n "${OPERATOR_NS}"
+----
+
+. Find the `deployment.yaml` key in the config map and add the annotations to the `spec.template.metadata.annotations` field as follows:
++
+[source,yaml]
+----
+deployment.yaml: |-
+  apiVersion: apps/v1
+  kind: Deployment
+  # --- truncated ---
+  spec:
+    template:
+      # --- truncated ---
+      metadata:
+        labels:
+         rhdh.redhat.com/app:  # placeholder for 'backstage-<cr-name>'
+        # --- truncated ---
+        annotations:
+          prometheus.io/scrape: 'true'
+          prometheus.io/path: '/metrics'
+          prometheus.io/port: '9464'
+          prometheus.io/scheme: 'http'
+  # --- truncated ---
+----
+
+. Save your changes.
+
+.Verification
+To verify if the scraping works:
+
+. Use `kubectl` to port-forward the Prometheus console to your local machine as follows:
++
+[source]
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
```
created_at: 2025-04-29T14:58:06Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,20 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. 
+
+
+.Prerequisites
+* You configured Prometheus for {eks-name} ({eks-short}) clusters, see link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.html[Prometheus metrics] in the Amazon documentation.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
```
created_at: 2025-04-29T15:00:26Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,20 @@
+= Monitoring with Amazon Prometheus
+
+{product} provides Prometheus metrics related to the running application. 
+
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
You can configure {product} to use Amazon Prometheus for comprehensive logging.
```
created_at: 2025-04-29T15:02:29Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,11 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
+= Monitoring and logging with Amazon Web Services (AWS) in {product}
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: themr0c
body: ```suggestion
= Monitoring and logging {product} on {aws-brand-name} ({aws-short})
```
created_at: 2025-04-29T15:07:27Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,19 @@
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+
+.Prerequisites
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: 

https://redhat-documentation.github.io/modular-docs/#assembly-guidelines

Assembly prerequisites

Prerequisites are conditions that must be satisfied before the user can start following the assembly and are applicable to all the modules in the assembly.

Use the second level heading syntax for the Prerequisites section in the assembly so that it is displayed in the table of contents and is consistent with the Additional resources or Next steps sections in the assembly.


```suggestion
== Prerequisites

```


created_at: 2025-04-29T15:18:50Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,20 @@
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+
+== Prerequisites
+
+* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
+* You ingested Prometheus metrics into the created workspace.
+
+.Next steps
+
+* You can configure the metrics scraping to extract data from pods based on specific pod annotations.
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion

include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]


include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]

== Next steps

* You can configure the metrics scraping to extract data from pods based on specific pod annotations.

```
created_at: 2025-04-29T15:20:26Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,22 @@
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+
+== Prerequisites
+
+* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
+* You ingested Prometheus metrics into the created workspace.
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]
+
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion


```
created_at: 2025-04-29T15:20:49Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,33 @@
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Helm chart
+
+You can configure the annotations for monitoring by using the {product} Helm chart.
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc
user: login: themr0c
body: ```suggestion
To enable logging to Amazon Prometheus, you can configure the required pod annotations by using the {product} Helm chart.
```
created_at: 2025-04-29T15:29:20Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,51 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Operator
+
+You can configure the annotations for monitoring by using the {product} Operator.
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
To enable logging to Amazon Prometheus, you can configure the required pod annotations by using the {product} Operator.
```
created_at: 2025-04-29T15:29:50Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,23 @@
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+
+== Prerequisites
+
+* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
+* You ingested Prometheus metrics into the created workspace.
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]
+
+
+== Next steps
+
+* You can configure the metrics scraping to extract data from pods based on specific pod annotations.
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
You can configure {product} to use Amazon Prometheus for comprehensive logging.
Amazon Prometheus extracts data from pods that have specific pod annotations.

== Prerequisites

* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
* You ingested Prometheus metrics into the created workspace.


include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc[leveloffset=+1]


include::modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc[leveloffset=+1]


```
created_at: 2025-04-29T15:33:08Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,21 @@
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+Amazon Prometheus extracts data from pods that have specific pod annotations.
+
+== Prerequisites
+
+* You link:https://docs.aws.amazon.com/eks/latest/userguide/prometheus.htm[configured Prometheus for your {eks-name} ({eks-short}) clusters].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-create-workspace.html[created an Amazon managed service for the Prometheus workspace].
+* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to ingest of the Developer Hub Prometheus metrics].
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
* You link:https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics.html[configured Prometheus to import the {product-short} metrics].
```
created_at: 2025-04-29T15:36:51Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,15 @@
+= Logging with Amazon CloudWatch logs
+
+Logging within the {product} relies on the link:https://github.com/winstonjs/winston[Winston library].
+The default logging level is `info`.
+To have more detailed logs, set the environment variable `LOG_LEVEL` to `debug` in your {product} instance.
path: assemblies/assembly-logging-with-amazon-cloudwatch-logs.adoc
user: login: themr0c
body: ```suggestion
To have more detailed logs, set the `LOG_LEVEL` environment variable to `debug` in your {product} instance.
```
created_at: 2025-04-29T15:40:07Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,16 @@
+= Configuring the application log level
path: modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc
user: login: themr0c
body: ```suggestion
= Configuring the application log level by using the {product} Helm chart
```
created_at: 2025-04-29T15:41:55Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,16 @@
+= Configuring the application log level by using the {product} Helm chart
path: modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-helm-chart.adoc
user: login: themr0c
body: ```suggestion
[id="configuring-the-application-log-level-by-using-the-helm-chart_{context}"]
= Configuring the application log level by using the {product} Helm chart
```
created_at: 2025-04-29T15:43:26Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,11 @@
+[id='proc-rhdh-monitoring-logging-aws_{context}']
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: themr0c
body: ```suggestion
[id="assembly-monitoring-and-logging-with-aws_{context}"]
```
created_at: 2025-04-29T15:44:16Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,15 @@
+= Logging with Amazon CloudWatch logs
path: assemblies/assembly-logging-with-amazon-cloudwatch-logs.adoc
user: login: themr0c
body: ```suggestion
[id="logging-with-amazon-cloudwatch_{context}"]
= Logging with Amazon CloudWatch
```
created_at: 2025-04-29T15:45:05Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,11 @@
+[id="assembly-monitoring-and-logging-with-aws_{context}"]
+= Monitoring and logging {product} on {aws-brand-name} ({aws-short})
+
+You can configure {product} to use Amazon CloudWatch for real-time monitoring and Amazon Prometheus for comprehensive logging.
+This is convenient when hosting {product-short} on {aws-brand-name} ({aws-short}) infrastructure.
+
+include::assembly-monitoring-with-amazon-prometheus.adoc[leveloffset=+1]
+
+
+include::assembly-logging-with-amazon-cloudwatch-logs.adoc[leveloffset=+1]
path: assemblies/assembly-monitoring-and-logging-with-aws.adoc
user: login: themr0c
body: ```suggestion
include::assembly-logging-with-amazon-cloudwatch.adoc[leveloffset=+1]
```
created_at: 2025-04-29T15:46:03Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,16 @@
+[id="logging-with-amazon-cloudwatch_{context}"]
path: assemblies/assembly-logging-with-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
[id="assembly-logging-with-amazon-cloudwatch_{context}"]
```
created_at: 2025-04-29T15:46:27Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,21 @@
+= Monitoring with Amazon Prometheus
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: ```suggestion
[id="assembly-monitoring-with-amazon-prometheus_{context}"]
= Monitoring with Amazon Prometheus
```
created_at: 2025-04-29T15:47:09Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,51 @@
+[id="configuring-annotations-for-monitoring-with-amazon-prometheur-by-using-the-operator_{context}"]
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
[id="configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-operator_{context}"]
```
created_at: 2025-04-29T15:47:49Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,33 @@
+= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Helm chart
path: modules/observe/proc-configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart.adoc
user: login: themr0c
body: ```suggestion
[id="configuring-annotations-for-monitoring-with-amazon-prometheus-by-using-the-helm-chart_{context}"]
= Configuring annotations for monitoring with Amazon Prometheus by using the {product} Helm chart
```
created_at: 2025-04-29T15:48:19Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,17 @@
+= Configuring the application log level by using the {product} Operator
path: modules/observe/proc-configuring-the-application-log-level-for-logging-with-amazon-cloudwatch-logs-by-using-the-operator.adoc
user: login: themr0c
body: ```suggestion
[id="configuring-the-application-log-level-by-using-the-operator_{context}"]
= Configuring the application log level by using the {product} Operator
```
created_at: 2025-04-29T15:49:09Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,22 @@
+[id="assembly-monitoring-with-amazon-prometheus_{context}"]
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+Amazon Prometheus extracts data from pods that have specific pod annotations.
+
+== Prerequisites
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: linfraze
body: We typically use the other heading type for Prerequisites. Is there a specific reason why you are using this type of heading here?

Doing it this way makes the Prerequisites section its own chapter. IMO, this section should be part of 2.1.
created_at: 2025-04-29T20:42:35Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,25 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
+
+* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+[subs="+quotes"]
+----
+/aws/containerinsights/_<cluster_name>_/application
+----
+
+.Procedure
+* Following is an example query to retrieve logs from the {product-short} instance:
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: linfraze
body: Convert this to an actionable procedural step. Currently, this is a statement rather than a step or action that the user can do. 
created_at: 2025-04-29T20:50:23Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,22 @@
+[id="assembly-monitoring-with-amazon-prometheus_{context}"]
+= Monitoring with Amazon Prometheus
+
+You can configure {product} to use Amazon Prometheus for comprehensive logging.
+Amazon Prometheus extracts data from pods that have specific pod annotations.
+
+== Prerequisites
path: assemblies/assembly-monitoring-with-amazon-prometheus.adoc
user: login: themr0c
body: Yes see https://redhat-documentation.github.io/modular-docs/#assembly-guidelines

> Assembly prerequisites
>
> Prerequisites are conditions that must be satisfied before the user can start following the assembly and are applicable to all the modules in the assembly.
>
> Use the second level heading syntax for the Prerequisites section in the assembly so that it is displayed in the table of contents and is consistent with the Additional resources or Next steps sections in the assembly.

created_at: 2025-04-30T06:23:47Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,25 @@
+[id="retrieving-logs-from-amazon-cloudwatch_{context}"]
+= Retrieving logs from Amazon CloudWatch
+
+.Prerequisites
+* CloudWatch Container Insights is used to capture logs and metrics for {eks-brand-name}.
+For more information, see https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html[Logging for {eks-brand-name}] documentation.
+
+* To capture the logs and metrics, link:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-addon.html[install the Amazon CloudWatch Observability EKS add-on] in your cluster.
+Following the setup of Container Insights, you can access container logs using Logs Insights or Live Tail views.
+
+* CloudWatch names the log group where all container logs are consolidated in the following manner:
++
+[subs="+quotes"]
+----
+/aws/containerinsights/_<cluster_name>_/application
+----
+
+.Procedure
+* Following is an example query to retrieve logs from the {product-short} instance:
path: modules/observe/proc-retrieving-logs-from-amazon-cloudwatch.adoc
user: login: themr0c
body: ```suggestion
* To retrieve logs from the {product-short} instance, run a query such as:
```
created_at: 2025-04-30T07:12:59Z
author_association: MEMBER

PR comments:
user: login: rhdh-bot
created_at: 2025-04-22T12:34:41Z
body: Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1089/ @ 04/30/25 07:15:13
author_association: COLLABORATOR
user: login: themr0c
created_at: 2025-04-29T15:55:02Z
body: /cherry-pick release-1.6
author_association: MEMBER
user: login: openshift-cherrypick-robot
created_at: 2025-04-29T15:55:05Z
body: @themr0c: once the present PR merges, I will cherry-pick it on top of `release-1.6` in a new PR and assign it to you.

<details>

In response to [this](https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/1089#issuecomment-2839425746):

>/cherry-pick release-1.6


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: CONTRIBUTOR
user: login: themr0c
created_at: 2025-04-29T15:57:49Z
body: @linfraze can you review again for leftovers? Feel free to merge.
author_association: MEMBER
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T07:15:01Z
body: @themr0c: new pull request created: #1118

<details>

In response to [this](https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/1089#issuecomment-2839425746):

>/cherry-pick release-1.6


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: CONTRIBUTOR