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

[Reporting] Update the documentation for 8.0 #113306

Closed
tsullivan opened this issue Sep 28, 2021 · 1 comment · Fixed by #114710
Closed

[Reporting] Update the documentation for 8.0 #113306

tsullivan opened this issue Sep 28, 2021 · 1 comment · Fixed by #114710
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead docs Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label

Comments

@tsullivan
Copy link
Member

tsullivan commented Sep 28, 2021

Kibana version: 8.0

  1. "Grant access with a custom index" is no longer relevant: system indices are not configurable in 8.0.
    https://www.elastic.co/guide/en/kibana/current/secure-reporting.html#_grant_access_with_a_custom_index

  2. This note should be removed:

    Reporting authenticates requests on the Kibana page only when the hostname matches the xpack.reporting.kibanaServer.hostname setting. Therefore Reporting fails if the set value redirects to another server. For that reason, "0" is an invalid setting because, in the Reporting browser, it becomes an automatic redirect to "0.0.0.0".
    In 8.0, setting "0" as the hostname stops Kibana from starting and the logs explain why. This is not specific to Reporting.

Linked issue: #114217

@tsullivan tsullivan added the bug Fixes for quality problems that affect the customer experience label Sep 28, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 28, 2021
@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 28, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Oct 4, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Oct 6, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:small Small Level of Effort and removed loe:medium Medium Level of Effort labels Sep 19, 2022
@sophiec20 sophiec20 added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 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 (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead docs Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants