public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: combines all SAML topics into one topic (#49443) (#49755)

Browse Source 
* Docs: combines all SAML topics into one topic (#49443)

* combines all SAML topics

* resolves merge conflicts

* makes prettier

(cherry picked from commit 8c84d62e3d)

* Fix broken relrefs

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
This commit is contained in:
Christopher Moyer
2022-05-31 09:27:07 -05:00
committed by GitHub
co-authored by Jack Baldry
parent adac77dd1f
commit 4b5adfb1ba
158 changed files with 729 additions and 663 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/image-rendering/_index.md
+1 -1
View File
@@ -143,7 +143,7 @@ RENDERING_MODE=reusable
#### Optimize the performance, CPU and memory usage of the image renderer
The performance and resources consumption of the different modes depend a lot on the number of concurrent requests your service is handling. To understand how many concurrent requests your service is handling, [monitor your image renderer service]({{< relref "./monitoring/" >}}).
The performance and resources consumption of the different modes depend a lot on the number of concurrent requests your service is handling. To understand how many concurrent requests your service is handling, [monitor your image renderer service]({{< relref "monitoring/" >}}).
With no concurrent requests, the different modes show very similar performance and CPU / memory usage.
docs/sources/image-rendering/monitoring.md
+1 -1
View File
@@ -14,7 +14,7 @@ weight: 100
# Monitoring the image renderer
Rendering images requires a lot of memory, mainly because Grafana creates browser instances in the background for the actual rendering. Monitoring your service can help you allocate the right amount of resources to your rendering service and set the right [rendering mode]({{< relref "./#rendering-mode" >}}).
Rendering images requires a lot of memory, mainly because Grafana creates browser instances in the background for the actual rendering. Monitoring your service can help you allocate the right amount of resources to your rendering service and set the right [rendering mode]({{< relref "/#rendering-mode" >}}).
## Enable Prometheus metrics endpoint
docs/sources/image-rendering/troubleshooting.md
+3 -3
View File
@@ -29,9 +29,9 @@ filters = rendering:debug
You can also enable more logs in image renderer service itself by:
- Increasing the [log level]({{< relref "./#log-level" >}}).
- Enabling [verbose logging]({{< relref "./#verbose-logging" >}}).
- [Capturing headless browser output]({{< relref "./#capture-browser-output" >}}).
- Increasing the [log level]({{< relref "/#log-level" >}}).
- Enabling [verbose logging]({{< relref "/#verbose-logging" >}}).
- [Capturing headless browser output]({{< relref "/#capture-browser-output" >}}).
## Missing libraries