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.

Sign up for GitHub

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

Jump to bottom

[Fleet]: Flickering Integration not verified banner is displayed under Elastic Defend integration. #209472

Open
sukhwindersingh-qasource opened this issue Feb 4, 2025 · 3 comments
Open

[Fleet]: Flickering Integration not verified banner is displayed under Elastic Defend integration. #209472

sukhwindersingh-qasource opened this issue Feb 4, 2025 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@sukhwindersingh-qasource
Copy link

sukhwindersingh-qasource commented Feb 4, 2025 •
edited
Loading

Kibana Build details:

VERSION: 8.18.0 BC1
BUILD: 82206
COMMIT: 33e6754

Preconditions:

  • Kibana cloud environment should be available.
  • A few agents should be installed.

Steps to reproduce:

  • Navigate to Intergrations tab.
  • Go to the Defend Integrations tab.
  • Edit the URL to check the commits, i.e., <Kibana_url>/status.
  • Click the browser's Back button.
  • Observe that the "Flickering Integration Not Verified" banner is displayed under Elastic Defend Integration

Expected Result:

  • "Flickering Integration Not Verified" banner should not be displayed under Elastic Defend Integration

What's working fine:

  • The issue is not observed for other integrations

Screen Recording:

Image

Elastic.Defend.-.Integrations.-.Elastic.Mozilla.Firefox.2025-02-04.14-44-27.mp4
@sukhwindersingh-qasource sukhwindersingh-qasource added bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Feb 4, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@sukhwindersingh-qasource
Copy link
Author

@amolnater-qasource Please review this

@amolnater-qasource
Copy link

Secondary review for this ticket is Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elasticmachine @amolnater-qasource @sukhwindersingh-qasource