Skip to content

Issues with Log level filtering on GCP #54

@gurpreetkh

Description

@gurpreetkh

Context:
Transactions and Fakerock use the /log pkg for their logging. While the log levels appear as expected in the logs, it seems like they are not correctly interpreted by GCP logging.

  • On GCP log console, filtering by SEVERITY>=ERROR or severity=ERROR shows all ERROR, INFO and DEBUG logs(if verbose enabled)
  • Filtering on INFO or DEBUG works as expected

Reference:
https://console.cloud.google.com/logs/viewer?interval=NO_LIMIT&project=anz-x-apps-np-e1bb39&minLogLevel=0&expandAll=false&timestamp=2020-05-25T21:48:04.367514516Z&customFacets=&limitCustomFacetWidth=true&advancedFilter=resource.type%3D%22k8s_container%22%0Aresource.labels.project_id%3D%22anz-x-apps-np-e1bb39%22%0Aresource.labels.location%3D%22australia-southeast1%22%0Aresource.labels.cluster_name%3D%22anz-x-apps-np-gke%22%0Aresource.labels.namespace_name%3D%22fabric-services-sit%22%0Aresource.labels.pod_name%3D%22transactions-v085-fzw8v%22%0Aresource.labels.container_name%3D%22transactions%22%0Aseverity%3E%3DERROR&scrollTimestamp=2020-05-25T07:17:55.506941691Z

This has been discussed with @anzboi who will be looking into this.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions