3.2. Logging with Amazon CloudWatch
Logging within the Red Hat Developer Hub relies on the Winston library.
3.2.1. Configuring the application log level by using the Red Hat Developer Hub Operator リンクのコピーリンクがクリップボードにコピーされました!
You can configure the application log level by using the Red Hat Developer Hub Operator.
Procedure
Modify the logging level by including the environment variable
LOG_LEVELin your custom resource as follows:spec: # Other fields omitted application: extraEnvs: envs: - name: LOG_LEVEL value: debug
3.2.2. Configuring the application log level by using the Red Hat Developer Hub Helm chart リンクのコピーリンクがクリップボードにコピーされました!
You can configure the application log level by using the Red Hat Developer Hub Helm chart.
Procedure
Modify the logging level by adding the environment variable
LOG_LEVELto your Helm chartvalues.yamlfile:upstream: backstage: # --- Truncated --- extraEnvVars: - name: LOG_LEVEL value: debug
3.2.3. Retrieving logs from Amazon CloudWatch リンクのコピーリンクがクリップボードにコピーされました!
Prerequisites
- CloudWatch Container Insights is used to capture logs and metrics for Amazon Elastic Kubernetes Service. For more information, see Logging for Amazon Elastic Kubernetes Service documentation.
- To capture the logs and metrics, 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/<cluster_name>/application
Procedure
To retrieve logs from the Developer Hub instance, run a query such as:
fields @timestamp, @message, kubernetes.container_name | filter kubernetes.container_name in ["install-dynamic-plugins", "backstage-backend"]