Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

involvedOject.kind doesnt work #165

Open
aporwal3 opened this issue Mar 7, 2024 · 0 comments
Open

involvedOject.kind doesnt work #165

aporwal3 opened this issue Mar 7, 2024 · 0 comments

Comments

@aporwal3
Copy link

aporwal3 commented Mar 7, 2024

Hi There,

Below is the config that we are using on our cluster

apiVersion: v1 kind: ConfigMap metadata: name: event-exporter-cfg namespace: monitoring data: config.yaml: | logLevel: debug logFormat: json maxEventAgeSeconds: 150 kubeQPS: 3000 kubeBurst: 15000 metricsNamePrefix: event_exporter_ route: routes: - drop: - namespace: "airflow-test" match: - receiver: "loki" receivers: - name: "loki" webhook: endpoint: "http://lgtm.svc.cluster.local:3100/loki/api/v1/push" headers: Content-Type: application/json User-Agent: "kube-event-exporter" streamName: "loki" layout: streams: - stream: app: kube-api source: event-exporter severity: "{{ .Type }}" reason: "{{ .Reason }}" name: "{{ .InvolvedObject.Name }}" namespace: "{{ .InvolvedObject.Namespace }}" kind: "{{ .InvolvedObject.Kind }}" host: "{{ .Source.Host }}" component: "{{ .Source.Component }}" values: - - "{{ mul .GetTimestampMs 1000000 }}" - "severity={{ .Type }} namespace={{ .InvolvedObject.Namespace }} kind={{ .InvolvedObject.Kind }} name={{ .InvolvedObject.Name }} reason={{ .Reason }} message={{ .Message }}"

But when we check on grafana we dont see values for InvolvedObject.Kind. We need this to identify the kind of the object which is failing

Please advise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant