-
Notifications
You must be signed in to change notification settings - Fork 187
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
latest version uses 100% CPU #43
Comments
Thank you @christophkluenter1234 for reporting this. Unfortunately I wasn't able to reproduce this issue. Can you provide some information how you've deployed prometheus-msteams? Did you use the helm chart? This error message indicates that the message card template does not have the key "sections" which is required for O365 Connector cards, and this exists in default-message-card.tmpl. |
I've just deployed off the helm chart 1.1.0 helm chart and I'm getting the same behavior as well. The only thing I changed from the chart values was the connector endpoint. At first glance it does look like the sections key is there.
|
Interesting. I'll have a look soon. |
Hi, |
Thanks for all the feedback. I will take a look into it latest on sunday. |
@kolikons, @psiservices-dstaples or @christophkluenter1234 can you please set log-level to DEBUG and provide more lines of the log output? I'd like to see the incoming prometheus alert. |
Hi @Knappek |
I merged the PR that avoids having thousands of lines of |
the latest version works as expected. No abnormal CPU usage anymore |
When running the latest version in kubernetes, we saw it using up 100% CPU.
The output was thousands of these lines:
Failed to parse json with key 'sections': Key path not found"
We don't overwrite the default template. So my first guess would be that
/default-message-card.tmpl might not be correct?
I will have another try on monday and report back.
The text was updated successfully, but these errors were encountered: