Skip to content

Log format unification for kyma module controllers #2005

@kwiatekus

Description

@kwiatekus

Description
Adjust logging in istio, so that deployments labelled with kyma-project.io/module=serverless produce logs that are compliant with recommendations documented here.

Configuration should be stored in a config map.
Logger configuration should be reloaded after changes (hot deploy).

Reason
Our goal is unify log format in order to reduce the time needed for users and support engineers to create error and warning log dumps.
kyma-project/cli#2651

Expected logs

  • make all log entries JSON parsable (aslo for operator)
  • include level : debug, info, warn, error
  • include timestamp (not ts) in RFC3339 format
  • include message (not msg)

Actual logs

{
  "level": "INFO",
  "timestamp": "2025-10-24T14:55:39Z",
  "caller": "state/deployment_status.go:53",
  "message": "deployment unhealthy: \"test-me-sdx6w\"",
  "context": {
    "request": "default/test-me"
  }
}
{
  "level": "INFO",
  "timestamp": "2025-10-24T14:55:39Z",
  "caller": "fsm/fsm.go:95",
  "message": "reconciliation done",
  "context": {
    "request": "default/test-me",
    "error": null,
    "result": {
      "Requeue": false,
      "RequeueAfter": 1000000000
    }
  }
}

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions