StatsCollection throwing exception making Kibana inaccessible #49204
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Telemetry
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
v7.5.0
Comments
|
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
tylersmalley
added
bug
|
All telemetry/collection code is wrapped in try/catch. We do only warn when errors happen. This error: Is happening at the task manager level failing to fetch elasticsearch (timing out) Are you sure you have elasticsearch running properly? @elastic/kibana-stack-services were there any changes in the task manager in |
|
That message is logged whenever an error occurs when asking Elasticsearch for tasks, and isn't new. We have made changes in how we fetch tasks, but the fact that the error says Request Timeout suggests Kibana failed to reach Elasticsearch, or at least, the call took too long. We'd need to see the other exceptions, as it's likely this TM error is a symptom of a broader problem with Kibana. What else does the log show? |
|
Elasticsearch was running prior to starting Kibana, which is why I thought this was strange. I restarted Kibana and it resolved the issue. If I see this again, is there anything else that would be useful to capture? I also created #49209 as I have been seeing it for quite some time, and am wondering if they are actually related to the error handling with tasks. |
|
Actually, turns out I do have the full logs. I wonder if we're not waiting for Kibana to be ready before running these tasks. full logs
|
This is a different issue, I believe @mikecote is already on it. :) |
|
I'm not sure when the Lens Telemetry task is scheduled, and it seems this error is coming from the I'm not familiar with the Telemetry Lens task, but it seems like a recent addition from a few days ago, perhaps @wylieconlon knows a bit more? |
|
We are introducing the Lens Telemetry task in 7.5, but I'm not sure I understand how this is connected to the timeout issue shown here. |
|
Pinging @elastic/pulse (Team:Pulse) |
|
It looks to me like this issue is not related to the telemetry/usageCollection plugins but rather a task in another plugin starting earlier than expected. I recall the Platform team working on some issues back in 7.5 (#51324 & #56950) with the ES re-connections (not sure if related, though). @tylersmalley do you think we can close this issue? |
I'll go ahead and close this issue. If any of you think it's still valid, feel free to reopen it, please. |
lukeelmers
added
Feature:Telemetry
Team:Core
|
Pinging @elastic/kibana-core (Team:Core) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the 7.5 branch from source, with Elasticsearch running. These exceptions were being thrown in additional to unhandled promise exceptions. I was not able to access Kibana at this time.
The text was updated successfully, but these errors were encountered: