FEAT / json logs wrong categorized in Datadog

[gmarcot]

Hey folks,

i ask you if possible to review the json logs format because is wrongly categorized in Datadog.

This is an example, those logs that driver-registrar have during the starting phase

{"ts":1721376983734.9492,"caller":"csi-node-driver-registrar/main.go:150","msg":"Version","v":0,"version":"v2.11.0"}
{"ts":1721376983734.97,"caller":"csi-node-driver-registrar/main.go:151","msg":"Running node-driver-registrar","v":0,"mode":""}
{"ts":1721376983734.9775,"caller":"csi-node-driver-registrar/main.go:172","msg":"Attempting to open a gRPC connection","v":1,"csiAddress":"/csi/csi.sock"}
{"ts":1721376987791.0059,"caller":"csi-node-driver-registrar/main.go:180","msg":"Calling CSI driver to discover driver name","v":1}
{"ts":1721376987793.5935,"caller":"csi-node-driver-registrar/main.go:189","msg":"CSI driver name","v":2,"csiDriverName":"ebs.csi.aws.com"}
{"ts":1721376987793.6306,"caller":"csi-node-driver-registrar/node_register.go:56","msg":"Starting Registration Server","v":0,"socketPath":"/registration/ebs.csi.aws.com-reg.sock"}
{"ts":1721376987793.8286,"caller":"csi-node-driver-registrar/node_register.go:66","msg":"Registration Server started","v":0,"socketPath":"/registration/ebs.csi.aws.com-reg.sock"}
{"ts":1721376987793.904,"caller":"csi-node-driver-registrar/node_register.go:96","msg":"Skipping HTTP server","v":0}
{"ts":1721376987876.7673,"caller":"csi-node-driver-registrar/main.go:96","msg":"Received GetInfo call","v":0,"request":"&InfoRequest{}"}
{"ts":1721376987911.4524,"caller":"csi-node-driver-registrar/main.go:108","msg":"Received NotifyRegistrationStatus call","v":0,"status":"&RegistrationStatus{PluginRegistered:true,Error:,}"}

are categorized as an ERROR

Many Thanks
Gianmarco

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten