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]: All policies using Logstash output is not displayed in the error while adding Fleet server integration to multiple policies. #190386

Closed
amolnater-qasource opened this issue Aug 13, 2024 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

Kibana Build details:

VERSION: 8.16.0 SNAPSHOT
BUILD: 77286
COMMIT: dcb16775f8192c2fc8ce629999da779e8b894413

Preconditions:

  1. 8.16.0 SNAPSHOT Kibana cloud environment should be available.
  2. Sample logstash output should be created and selected by a few agent policies.

Steps to reproduce:

  1. Navigate to Integration>Fleet Server.
  2. Click Add Fleet Server integration>Existing agent policies>select multiple integrations including policies using logstash output.
  3. Click Save and continue button.
  4. Observe error is displayed for 1 integration.
  5. Remove this integration and click Save and continue button again.
  6. Observe error is displayed for another integration.
  7. Untill all the policies using logstash output are not removed user isn't able to save the policy.[Expected]

Expected Result:
All policies using Logstash output should be displayed in the error while adding Fleet server integration to multiple policies.

Screen Recording:

Add.integration.-.Fleet.Server.-.Integrations.-.Elastic.-.Google.Chrome.2024-08-13.12-01-23.mp4

Feature:
#75867

@amolnater-qasource amolnater-qasource added bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Aug 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@karanbirsingh-qasource Please review.

@ghost
Copy link

ghost commented Aug 13, 2024

secondary review of this ticket is done

@nchaulet nchaulet assigned nchaulet and unassigned nchaulet Sep 18, 2024
@jen-huang
Copy link
Contributor

IMO this behavior is okay because we try to fail fast on the backend. We check the compatibility of agent policies one by one and fail immediately when an issue is found, instead of "bulk checking" at once. Closing as won't fix. cc @kpollich

@jen-huang jen-huang closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2024
@amolnater-qasource
Copy link
Author

Thank you for confirming the expected behavior @jen-huang

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 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

5 participants