Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fleet policy output fields disabled in Basic subscription without explanation #148839

Open
runejuhl opened this issue Jan 12, 2023 · 1 comment
Open
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@runejuhl
Copy link

Kibana version: 8.5.2

Elasticsearch version: N/A

Server OS version: N/A

Browser version: N/A

Browser OS version: N/A

Original install method (e.g. download page, yum, from source, etc.): N/A

Describe the bug:

When configuring Fleet policy outputs the form fields are disabled, and there is not indication as to why this is, as shown in the screenshot below:

image

This caused me quite a bit of frustration and cost me some time, as I initially suspected that the Fleet output configuration itself was to blame.

Adding a help text to the form when the subscription doesn't allow configuring Fleet policy outputs would have prevented this.

Steps to reproduce:

  1. Install and configure Elasticsearch, Kibana and Fleet using the Basic (free) subscription
  2. Try to change Fleet output per Fleet policy

Expected behavior:

A help text should be shown when the form fields are disabled due to subscription.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

I'm not well versed in modern (JS-based) web development, but I imagine
that something like I've done in runejuhl@24fc434 could do the trick. Let me know if you want me to open a PR.

@runejuhl runejuhl added the bug Fixes for quality problems that affect the customer experience label Jan 12, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 12, 2023
@rayafratkina rayafratkina added the Team:Fleet Team label for Observability Data Collection Fleet team label Jan 13, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants