Configuration

Owned by shivam Upadhyay
Last updated: Sept 09, 2024
11 min read

 

Latest Monitoring Chart is available here.

# Clone git repository git clone https://github.com/egovernments/DIGIT-DevOps.git cd DIGIT-DevOps # Checkout to "digit-lts-monitoring" branch git checkout digit-lts-monitoring

Helmfile

Update the environments as required with their relevant file-paths of environment & secrets file and the namespace to be used.

In below config "demo" is the environment with default namespace being set & environment files being provided.

# deploy-as-code/helm/charts/monitoring/monitoring-helmfile.yaml environments: demo: values: - namespace: monitoring - ../../environments/egov-demo.yaml - ../../environments/egov-demo-secrets.yaml

 

Environment Files

Grafana

  1. GitHub OAuth App Creation

    • Follow the GitHub OAuth app

    • Homepage URL
      https://<your_domain_name>

    • Authorization callback URL
      https://<your_domain_name>/monitoring/login/github

    • Generate Client ID & Client secret

  2. Update Client ID & Client secret in secrets config.

    # deploy-as-code/helm/environments/egov-demo-secrets.yaml cluster-configs: secrets: grafana: clientID: <OAuth-key> clientSecret: <OAuth-token>

  3. Update environment config to allow GitHub organization & teams specific role-based access

Note: Valid roles are None, Viewer, Editor, Admin or GrafanaAdmin
Visit official documentation for more information Grafana GitHub OAuth

 

Loki Stack

Filesystem as a storage

 

s3 as storage

Caution: Use the sub claim instead of aud when setting up Web Identity (OIDC) IAM roles to ensure correct identity matching.

  1. Create AWS Web Identity (OIDC) IAM role with following policy.

     

  2. Update s3 details & role ARN in below config.

Note: Refer to official docs for detailed configuration

 

Prometheus

Alerting

Slack Alerts

Email Alerts