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

[8.11] [DOCS] Linking reporting and sharing page with configure reporting page (#171977) #172048

Merged
merged 1 commit into from
Nov 28, 2023
Merged

[8.11] [DOCS] Linking reporting and sharing page with configure reporting page (#171977) #172048

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/setup/configuring-reporting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ Granting the privilege to generate reports also grants the user the privilege to
==== Grant access with the role API
With <<grant-user-access, {kib} application privileges>> enabled in Reporting, you can also use the {ref}/security-api-put-role.html[role API] to grant access to the {report-features}, using *All* privileges, or sub-feature privileges.

NOTE: this [API request](https://www.elastic.co/guide/en/kibana/current/role-management-api-put.html) needs to be executed against the Kibana API endpoint
NOTE: This link:https://www.elastic.co/guide/en/kibana/current/role-management-api-put.html[API request] needs to be executed against the link:https://www.elastic.co/guide/en/kibana/current/api.html[Kibana API endpoint].
[source, sh]
---------------------------------------------------------------
POST <kibana host>:<port>/api/_security/role/custom_reporting_user
Expand Down Expand Up @@ -229,3 +229,5 @@ For more information, see {ref}/notification-settings.html#ssl-notification-sett
. Add one or more users who have access to the {report-features}.
+
Once you've enabled SSL for {kib}, all requests to the reporting endpoints must include valid credentials.

For more information on sharing reports, direct links, and more, refer to <<reporting-getting-started, Reporting and sharing>>.
2 changes: 2 additions & 0 deletions docs/user/reporting/index.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ You access the options from the *Share* menu in the toolbar. The sharing options
NOTE: For Elastic Cloud deployments, {kib} instances require a minimum of 2GB RAM to generate PDF or PNG reports. To
change {kib} sizing, {ess-console}[edit the deployment].

For more information on how to configure reporting in {kib}, refer to <<secure-reporting,Configure reporting in {kib}>>

[float]
[[manually-generate-reports]]
== Create reports
Expand Down
Loading