forked from opsgenie/kubernetes-event-exporter
-
Notifications
You must be signed in to change notification settings - Fork 163
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
event discarded #184
Comments
please help. |
same problem, have you solved ? |
No, I haven't resolved it yet, but I have written a job to reset my
kube-event-exporter pods across the entire cluster every 24 hours.
…On Tue, Sep 10, 2024 at 11:18 AM Cloud-Shen ***@***.***> wrote:
i see the log 'Event discarded as being older then maxEventAgeSeconds' in
my loki and see client-side throttling with lots of 0 on my pod logs. i add
kubeQPS: 100 and kubeBurst: 500 to my config map and my maxEventAge is 300
and it works good about 24 hours after that again i see Event discarded as
being older then maxEventAgeSeconds.
same problem, have you solved ?
—
Reply to this email directly, view it on GitHub
<#184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS3XO6XDSCKPGKASK6424EDZV2P3FAVCNFSM6AAAAABILMPKNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZZHEYTQMZRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i see the log 'Event discarded as being older then maxEventAgeSeconds' in my loki and see client-side throttling with lots of 0 on my pod logs.
i add kubeQPS: 100 and kubeBurst: 500 to my config map and my maxEventAge is 300 and it works good about 24 hours after that again i see Event discarded as being older then maxEventAgeSeconds.
The text was updated successfully, but these errors were encountered: