Configuring Logging

Setting up logging
The Logs tab

Figure 1 - The Logs tab

Here are the details of these fields:

Loki Logs Storage Configuration

Logs Bucket | Logs Region

The name of the bucket where your Loki logs should be stored and the region where the bucket is hosted. The bucket is used internally by the ACM; it’s not accessible by users. In addition, this setting is only used for Bring Your Own Kubernetes (BYOK) environments. For Bring Your Own Cloud (BYOC) environments, the bucket is configured automatically and these fields are not editable.

Send Logs to an External Loki service

External Loki URL

The URL of your external Loki server in the format https://username:password@lokiserver.com/api/prom/push. For complete details on integrating your Altinity.Cloud environment with an external Loki server, see the Administrator Guide section on Integrating Loki.

Sending Logs to an S3 bucket in a BYOK environment

If you have a BYOK environment on AWS, you can create an S3 bucket for logs. (That is an S3-compatible bucket; it can be running at AWS, CloudFlare R2, Backblaze, or any other S3-compatible storage vendor.) There are two steps:

  1. Create the bucket you want to use and set up its authorization credentials (username and password)
  2. Create a secret named S3_BASIC_AUTH with that username and password:
kubectl create secret generic log-storage-s3-basic-auth \
  --namespace=altinity-cloud-system \
  --from-literal=S3_BASIC_AUTH='username:password'

Or, in YAML:

apiVersion: v1
kind: Secret
metadata:
  name: log-storage-s3-basic-auth
  namespace: altinity-cloud-system
type: Opaque
stringData:
  S3_BASIC_AUTH: "username:password"

Once the secret and bucket are created, you can enter the name of the bucket and its region in the Logging tab of the Environment configuration dialog in Figure 1 above.