[ResponseOps][Reporting] stop toasting "Could not check Reporting job status!" #245184
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… status!" resolves elastic#216181 Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana goes down. Not useful, so removed.
pmuellr
added
release_note:skip
Contributor
💚 Build Succeeded
Metrics [docs]Page load bundle
History
|
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
darnautov
reviewed
Dec 5, 2025
| ); | ||
| window.console.error(err); | ||
| // Seems to only occur when the connection to Kibana fails. | ||
| // We used to toast here, but ... it was very noisy. |
Contributor
There was a problem hiding this comment.
@pmuellr I think it’d be better to keep the error toast, just make it behave more user-friendly. I have two suggestions:
-
Use the polling interval to control toast lifetime
We start polling with an interval here.
We could pass thisintervalto thefindChangedStatusJobsmethod and then set{ toastLifeTimeMs: interval }when callingtoasts.addDanger. -
Track and remove the existing toast
- Define
private connectionErrorToast: Toast | undefined; - Assign it when showing the toast:
this.connectionErrorToast = this.core.notifications.toasts.addDanger(...) - In each
findChangedStatusJobscall, check if it exists and remove it:
this.core.notifications.toasts.remove(this.connectionErrorToast);
WDYT?
Contributor
Author
In addition to those, I think the only reason to keep the toast is if Kibana isn't actually down, but the job polling is generating errors. So that means it needs to be tied into Kibana availability as well. So ... it gets complicated. I'm going to suggest we defer that to a separate issue. My experience is the only time these toasts are ever seen is when Kibana is down / inaccessible, in which case the system provide a standard not-toast message about Kibana not being available. So right now, they add no value, and in fact may obscure the system-generated not-toast message (visually). |
darnautov
approved these changes
Dec 10, 2025
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 https://github.com/elastic/kibana/actions/runs/20117036141 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 10, 2025
… status!" (elastic#245184) resolves elastic#216181 Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana becomes unavailable. Not useful, so removed. (cherry picked from commit b53f22d)
Contributor
kibanamachine
added a commit
that referenced
this pull request
Dec 11, 2025
…ng job status!" (#245184) (#245937) # Backport This will backport the following commits from `main` to `9.2`: - [[ResponseOps][Reporting] stop toasting "Could not check Reporting job status!" (#245184)](#245184) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-12-10T23:50:35Z","message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:all-open","Feature:Reporting:Framework","Feature:Reporting:Screenshot","v9.3.0"],"title":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\"","number":245184,"url":"https://github.com/elastic/kibana/pull/245184","mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245184","number":245184,"mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}}]}] BACKPORT--> Co-authored-by: Patrick Mueller <patrick.mueller@elastic.co>
pmuellr
added a commit
to pmuellr/kibana
that referenced
this pull request
Dec 11, 2025
… status!" (elastic#245184) resolves elastic#216181 Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana becomes unavailable. Not useful, so removed. (cherry picked from commit b53f22d) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
pmuellr
added a commit
to pmuellr/kibana
that referenced
this pull request
Dec 11, 2025
… status!" (elastic#245184) resolves elastic#216181 Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana becomes unavailable. Not useful, so removed. (cherry picked from commit b53f22d) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
pmuellr
added a commit
that referenced
this pull request
Dec 11, 2025
…ng job status!" (#245184) (#245945) # Backport This will backport the following commits from `main` to `9.1`: - [[ResponseOps][Reporting] stop toasting "Could not check Reporting job status!" (#245184)](#245184) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-12-10T23:50:35Z","message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:all-open","Feature:Reporting:Framework","Feature:Reporting:Screenshot","v9.3.0"],"title":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\"","number":245184,"url":"https://github.com/elastic/kibana/pull/245184","mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245184","number":245184,"mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}},{"url":"https://github.com/elastic/kibana/pull/245937","number":245937,"branch":"9.2","state":"OPEN"}]}] BACKPORT-->
pmuellr
added a commit
that referenced
this pull request
Dec 11, 2025
…ing job status!" (#245184) (#245946) # Backport This will backport the following commits from `main` to `8.19`: - [[ResponseOps][Reporting] stop toasting "Could not check Reporting job status!" (#245184)](#245184) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-12-10T23:50:35Z","message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:all-open","Feature:Reporting:Framework","Feature:Reporting:Screenshot","v9.3.0"],"title":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\"","number":245184,"url":"https://github.com/elastic/kibana/pull/245184","mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245184","number":245184,"mergeCommit":{"message":"[ResponseOps][Reporting] stop toasting \"Could not check Reporting job status!\" (#245184)\n\nresolves https://github.com/elastic/kibana/issues/216181\n\nRemoves the toast that popped up, every few seconds, informing us that\n\"Could not check Reporting job status!\", when Kibana becomes\nunavailable. Not useful, so removed.","sha":"b53f22d6c324a7e2362197731d17562d01dd5821"}},{"url":"https://github.com/elastic/kibana/pull/245937","number":245937,"branch":"9.2","state":"OPEN"}]}] BACKPORT-->
seanrathier
pushed a commit
to seanrathier/kibana
that referenced
this pull request
Dec 15, 2025
… status!" (elastic#245184) resolves elastic#216181 Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana becomes unavailable. Not useful, so removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #216181
Summary
Removes the toast that popped up, every few seconds, informing us that "Could not check Reporting job status!", when Kibana becomes unavailable. Not useful, so removed.
To validate
Reproduce the old behaviour on
main:With this PR, the infinite toasts don't occur, but there is a
Failed to fetchthat is not a toast like other one, just a message that's updated with a recurring count.Not sure where this is coming from, guessing it may be an ES client thing, where we're still making the ES requests to check the status. I think this is survivable - the infinite toasts was maddening! We can open an issue later if this becomes problematic. We'd probably need to hook into some ES available observer, and start/stop the status checks around that, which could get complicated ...
a little later ...
While investigating and repro-ing a separate DOS issue in Kibana, I happened to notice the
Failed to fetchmessage appear in a completely unrelated UX. This seems right to me, that somehow the platform is generating these. Makes sense, and I think that means the lingering "not nearly as annoying as the infinite toast" messageFailed to fetchis fine ...