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

Large number of events are missing, the same event can only be received once #197

Open
wangjinxiang0522 opened this issue Aug 13, 2024 · 3 comments

Comments

@wangjinxiang0522
Copy link

Hi
Im running version 1.7.

My configuration is

config:
  logLevel: debug
  kubeQPS: 100
  kubeBurst: 500
  maxEventAgeSeconds: 600
  metricsNamePrefix: 'event_exporter_'
  logFormat: json
  receivers:
    - name: "dump"
      file:
        path: "/dev/stdout"
        layout:
           message: "{{ .Message }}"
           reason: "{{ .Reason }}"
           type: "{{ .Type }}"
           count: "{{ .Count }}"
           kind: "{{ .InvolvedObject.Kind }}"
           name: "{{ .InvolvedObject.Name }}"
           namespace: "{{ .Namespace }}"
           component: "{{ .Source.Component }}"
           host: "{{ .Source.Host }}"

    - name: "loki"
      loki:
        streamLabels:
          application: kube-api
          container: event-exporter
        url: http://loki-gateway.stage.sprucetec.com/loki/api/v1/push
        tls:
          insecure: true
  route:
    routes:
      - match:
          - receiver: "loki"
          - receiver: "dump"

nodeSelector:
  node-type: monitoring

image:
  registry: reg.sprucetec.com
  repository: monitor/kubernetes-event-exporter
  tag: 1.6.1-debian-12-r16

I reviewed the source code and found that the OnUpdate method is not implemented. Is this the reason why the same event can only be received once?

@jarnfast
Copy link

You're correct. The problem has been addressed in multiple PRs. The quick fix in #168 and with a bit more configuration in #167

Until either PR gets handled I elected to build it myself with the fix provided in #168 ;-)

@tuxerrante
Copy link

Hi @jarnfast
it seems also #168 is stuck since a while, any plan to merge this feature soon?
Thanks

@jarnfast
Copy link

Hi @jarnfast it seems also #168 is stuck since a while, any plan to merge this feature soon? Thanks

All PRs seem to be stuck - unfortunately I cannot help with merging them. Maybe pinging @mustafaakin can do the trick?

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

3 participants