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]: Remote ES not supported error is displayed on Editing shared Elastic Defend when one policy has Remote ES selected as Default output for integrations. #197752

Open
amolnater-qasource opened this issue Oct 25, 2024 · 2 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

amolnater-qasource commented Oct 25, 2024

Kibana Build details:

VERSION: 8.16.0 BC2
BUILD: 79434
COMMIT: 59220e984f2e3ca8b99fe904d077a5979f5f298d

Preconditions:

  1. 8.16.0-BC1 Kibana cloud environment should be available.
  2. Remote ES should be added.

Steps to reproduce:

  1. Navigate to Fleet>Agent policy tab.
  2. Select Remote ES as output for integration for one policy.
  3. Add fleet-server integration to this policy with default ES output.
  4. Now add Elastic Defend to a few policies as shared integration.
  5. Navigate to Integrations>Elastic Defend>Integration policies.
  6. Click + icon and update the policies and add policy with Remote ES selected.
  7. Observe error: Output of type "remote_elasticsearch" is not usable with policy "Agent policy 6".
    Expected Result:
    Remote ES not supported error should not displayed on Editing shared Elastic Defend when one policy has Remote ES selected as Default output for integrations.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-10-24.16-03-53.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 Oct 25, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@muskangulati-qasource Please review.

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

2 participants