You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Saw a similar post with this problem. When I try and install via Helm chart the default Grafana chart showed very long ping times; circa ~3 seconds for some larger clusters, and even a ten node cluster is showing ~1 to ~2 second ping times.
As one user has done, I made a new build and instrumented out the calls a bit and the reported time seems accurate, but when I hit the /ping endpoints directly from pods with other tools like a timed curl the time seems much more reasonable (~a few mills).
The text was updated successfully, but these errors were encountered:
Ford thing to check would be your CPU limits - you might be starving them
for CPU time.
On Fri, 7 Oct 2022 at 06:34, Montana Mendy ***@***.***> wrote:
Hey all,
Saw a similar post with this problem. When I try and install via Helm
chart the default Grafana chart showed very long ping times; circa ~3
seconds for some larger clusters, and even a ten node cluster is showing ~1
to ~2 second ping times.
As one user has done, I made a new build and instrumented out the calls a
bit and the reported time seems accurate, but when I hit the /ping
endpoints directly from pods with other tools like a timed curl the time
seems much more reasonable (~a few mills).
—
Reply to this email directly, view it on GitHub
<#125>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVIOWUZZH7PSPULB3CAVTWB6Y7VANCNFSM6AAAAAAQ7IF2DI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Best regards,
Mikolaj Pawlikowski
+44 747 330 2049
Hey all,
Saw a similar post with this problem. When I try and install via Helm chart the default Grafana chart showed very long ping times; circa ~3 seconds for some larger clusters, and even a ten node cluster is showing ~1 to ~2 second ping times.
As one user has done, I made a new build and instrumented out the calls a bit and the reported time seems accurate, but when I hit the
/ping
endpoints directly from pods with other tools like a timedcurl
the time seems much more reasonable (~a few mills).The text was updated successfully, but these errors were encountered: