Aller au contenu

Logging#

Important

Next steps should be done after the zone has been removed from zones.cue (by Automation team).

Envs-ng configuration update#

It is possible to have zone-specific configurations in envs-ng which have to be removed.

cd caascad/terraform/envs-ng
git checkout -b "decom_${ZONE_NAME}_logging" #create a new git branch
grep -r "$ZONE_NAME" *.cue # only in files managed by monitoring team

If some files were found,

  • remove the references to the zone in the matching lines
  • create a MR and ask for validation
  • merge it into master branch

Checkpoints#

The points to verify are defined in the Jira template. Here are some details: 

No references to the Loki zone:

(x) in envs-ng
(x) in Vault (path: {{zones/fe}})
(x) in the documentation

In the FE console, no resources related to the Loki zone:
(x) S3 buckets

Silences:
(x) no alerts/silences in Karma

Grafana:
(x) absence of the Loki datasource