[Uptime] Uptime index config using kibana.yml#115775
[Uptime] Uptime index config using kibana.yml#115775shahzad31 merged 6 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/uptime (Team:uptime) |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
justinkambic
left a comment
There was a problem hiding this comment.
I encountered an error after setting this. Is there some additional configuration I need to do in order to get this working?
Saw error logs like this in Kibana server log:
[2021-10-20T16:37:30.230-04:00][ERROR][http] ResponseError: security_exception: [no_such_remote_cluster_exception] Reason: no such remote cluster: [remote_cluster]
@justinkambic no, it should just work, what key you were using? |
|
@elasticmachine merge upstream |
|
@shahzad31 still seeing that error, my only config entry is: We can pair if you want to see, not sure how to debug. |
I actually had remote_cluster: configured using olbt-cli, in your case, you just need to add your heartbeat index pattern like heartbeat-* |
|
@elasticmachine merge upstream |
|
Ok, this works in that case. We may want to create a follow-up to improve error handling where CCS is not configured. Lots of nasty error messages show up in the Kibana log for unrelated components of the app. |
justinkambic
left a comment
There was a problem hiding this comment.
LGTM. One nit comment.
| } | ||
|
|
||
| public setup(core: CoreSetup, plugins: UptimeCorePlugins) { | ||
| const config = this.initContext.config.get<UptimeConfig>(); |
There was a problem hiding this comment.
We can probably skip this declaration, since we're only using the symbol one time right below here.
💛 Build succeeded, but was flaky
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
💔 Backport failedThe backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…-migrate-away-from-injected-css-js * 'master' of github.com:elastic/kibana: (61 commits) [ML] Nodes overview for the Model Management page (elastic#116361) [Uptime] Uptime index config using kibana.yml (elastic#115775) [Controls] Dashboard Integration (elastic#115991) skip flaky suite (elastic#104260) Include Files in GitHub UI (elastic#115956) skip flaky suite (elastic#116060) [Canvas] By-Value Embeddables (elastic#113827) Skip failing test (elastic#115366) [Osquery] Fix live query search doesn't return relevant results for agents (elastic#116332) [Integrations] Added link in old Add Data description and fixed alignment in cards (elastic#116213) [Actions] Extended ActionTypeRegistry with connector validation to validate config with secrets (elastic#116079) skip flaky suite (elastic#109329) Grant access to machine learning features when base privileges are used (elastic#115444) Skipping failing test (elastic#84957) [RAC][Security Solution] Adds migration to new SecuritySolution rule types (elastic#112113) skip flaky suite (elastic#115366) [Fleet] Marking API spec as experimental (elastic#116331) [Docs] Cleaning up the versions in the upgrade paths. Closes elastic#116223 (elastic#116228) [Reporting] Suppress debug logs in the mock logger (elastic#116012) [Metrics UI] Clear threshold alert groups state when filterQuery changes (elastic#116205) ... # Conflicts: # src/plugins/dashboard/public/application/embeddable/dashboard_container.tsx # src/plugins/dashboard/public/types.ts
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |

Summary
Fix #115774
Now you can config uptime index settings using kibana.yml key
xpack.uptime.index: remote_cluster:heartbeat-*This will allow robots team to config ccs with new olbt-cli setup
Testing
set the key for above config and check that when uptime settings page loads,
it show that key
but when user override it, saved objects uptime settings should take precedence