Repository navigation
Conversation
There is no preconfigured reduced plugin set for classic (non-serverless) Kibana; the serverless.*.yml files are the only precedent. This adds a validated "lite" configuration that disables the plugins that expose an unconditional top-level `enabled` flag in classic mode: securitySolution, canvas, monitoring, cases, agentBuilder, automatic_import, workflowsManagement, newsfeed, interactiveSetup which transitively disables 18 more plugins (timelines, sessionView, alertingVTwo, significantEvents, observabilityAgentBuilder, ...). Discover, Dashboard, Visualize, alerting, and stack management remain enabled. Measured on an idle dev server: idle heap_used drops from ~650-700 MB (with the swc-register fs-cache fix) to ~550-560 MB, and startup to "available" takes ~24 s. Usage: node scripts/kibana --dev -c config/kibana.yml -c config/kibana.lite.yml Most stack-management plugins (ilm, ccr, watcher, rollup, snapshot_restore, remote_clusters, license_management, graph) expose `enabled` only via offeringBasedSchema (serverless) and cannot be disabled in classic mode; ml and fleet have no top-level flag at all. Making more plugins disableable in classic would allow further cuts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
There is no preconfigured reduced plugin set for classic (non-serverless) Kibana — the
serverless.*.ymlfiles are the only precedent. This adds a validatedconfig/kibana.lite.ymlthat disables every plugin exposing an unconditional top-levelenabledflag in classic mode:securitySolution,canvas,monitoring,cases,agentBuilder,automatic_import,workflowsManagement,newsfeed,interactiveSetupwhich transitively disables 18 more plugins (timelines, sessionView, alertingVTwo, significantEvents, observabilityAgentBuilder, …). Discover, Dashboard, Visualize, alerting, and stack management remain enabled.
Usage:
Measured impact (idle dev server, classic stateful)
Notes for reviewers
enabledonly viaofferingBasedSchema(serverless) and cannot be disabled in classic mode; ml and fleet have no top-level flag at all. Making more plugins disableable in classic would be the cheapest path to further memory cuts.config/of the distributable or should live as a documented dev-only recipe. Happy to move it if the latter is preferred.Related: #300785 (dev transpile cache), #300786 (lazy-loading heavy server deps).
🤖 Generated with Claude Code