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

[Obs SLO] Confirm new CDN is working in the observability SLO pages #178500

Closed
jasonrhodes opened this issue Mar 12, 2024 · 4 comments
Closed

[Obs SLO] Confirm new CDN is working in the observability SLO pages #178500

jasonrhodes opened this issue Mar 12, 2024 · 4 comments
Assignees
Labels
Feature:SLO Team:obs-ux-management Observability Management User Experience Team

Comments

@jasonrhodes
Copy link
Member

Kibana core team is ready for us to do some initial testing on the Kibana serverless CDN.

Acceptance Criteria

  • Follow the steps in this Google Doc (copied from @jloleysens email) re: setting up a QA project
  • Do manual QA in the project for the observability SLO pages
    • Keep your network tab open to ensure asset loading and JS initiated requests work as expected
    • If you have JS code in the browser that is calling domains other than origin or *.elastic.co please reach out to us, your requests will be blocked!
  • Document any problems or concerns in this issue and then report them to the Kibana core team (in the #kibana-core Slack channel was the recommended way)

Timebox: 1-2 hours
Due Date: 22 March

@jasonrhodes jasonrhodes added Feature:SLO Team:obs-ux-management Observability Management User Experience Team labels Mar 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@simianhacker
Copy link
Member

The only issue I see is this:

image

Which seems unrelated to the CDN.

@jasonrhodes
Copy link
Member Author

I think that's related to the "If you have JS code in the browser that is calling domains other than origin or *.elastic.co please reach out to us, your requests will be blocked!" warning, and probably means our RUM requests are failing. I'll check with folks who know more about RUM to confirm.

@jasonrhodes
Copy link
Member Author

It's been solved already: #178391 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:SLO Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Development

No branches or pull requests

3 participants