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]: Unable to set default output for Integrations for Remote Elasticsearch output. #173984

Closed
amolnater-qasource opened this issue Dec 27, 2023 · 5 comments · Fixed by #174056
Assignees
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. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

amolnater-qasource commented Dec 27, 2023

UPDATED ISSUE AS PER CHANGES UNDER #173353

Kibana Build details:

VERSION: 8.12.0 BC3
BUILD: 69985
COMMIT: 2a8afed8572a4c709aa1c64216748197eeb9b18f
Artifact Link: https://staging.elastic.co/8.12.0-61156bc6/summary-8.12.0.html

Host OS: All

Preconditions:

  1. 8.12.0 BC3 Kibana cloud environment should be available.

Steps to reproduce:

  1. Navigate to Fleet Settings.
  2. Add/Edit Remote Elasticsearch output.
  3. Observe user is able to enable/disable default for integrations output for Remote Elasticsearch.
  4. Enable the default for integrations toggle and save the settings.
  5. Observe the Remote Elasticsearch is not set as default for output for integrations.

Screen Recording:

Settings.-.Fleet.-.Elastic.-.Google.Chrome.2023-12-27.15-55-07.mp4

Expected Result:
User should be able to set default output for Integrations for Remote Elasticsearch output.

Feature:
#104986

@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 Dec 27, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@manishgupta-qasource Please review.

@manishgupta-qasource
Copy link

Secondary review for this ticket is Done

@amolnater-qasource amolnater-qasource changed the title [Fleet]: Set default output for Integrations toggle is not disabled for Remote Elasticsearch output. [Fleet]: Unable to set default output for Integrations toggle for Remote Elasticsearch output. Dec 29, 2023
@amolnater-qasource amolnater-qasource changed the title [Fleet]: Unable to set default output for Integrations toggle for Remote Elasticsearch output. [Fleet]: Unable to set default output for Integrations for Remote Elasticsearch output. Dec 29, 2023
@amolnater-qasource
Copy link
Author

Hi Team,

We have revalidated this issue on latest 8.12.0 BC4 and found it reproducible there too.

Observations:

  • Unable to set default output for integrations for Remote Elasticsearch output.

Build details:
VERSION: 8.12.0 BC4
BUILD: 70016
COMMIT: c2fda47

Screen Recording:

Settings.-.Fleet.-.Elastic.-.Google.Chrome.2023-12-29.14-41-06.mp4

Impacted Testcase:

Please let us know if anything else is required from our end.
Thanks!

@amolnater-qasource
Copy link
Author

Hi Team,

We have revalidated this issue on latest 8.12.0 BC5 kibana cloud environment and found it fixed now.

Observations:

  • We are able to set default output for Integrations for Remote Elasticsearch output.

Build details:
VERSION: 8.12.0 BC5
BUILD: 70053
COMMIT: db9b892
Artifact Link: https://staging.elastic.co/8.12.0-9f05a310/downloads/beats/elastic-agent/elastic-agent-8.12.0-windows-x86_64.zip

Screenshot:
image

Hence we are closing this issue and marking as QA:Validated.

Thanks!

@amolnater-qasource amolnater-qasource added QA:Validated Issue has been validated by QA and removed QA:Ready for Testing Code is merged and ready for QA to validate labels Jan 10, 2024
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. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants