Docs: Setup refactor (#49739)
* builds out refactored setup topics * Automatically fix some relrefs with mv-manager Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Use refs for tutorials content which is outside of this repository Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Manually fix complicated relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * consolidates team sync and db encryption topics * Fix relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * updates setup index file * Convert TOML to YAML Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Add current alias for new alerting content Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Add current aliases to new setup-grafana and configure-security pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/setup-grafana/configure-grafana/_index.md Co-authored-by: Torkel Ödegaard <torkel@grafana.com> * moves saml docs, updates order in TOC * Manually fix relrefs Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * added usage insights topics, adjusted weights * corrected relrefs * Fix relrefs broken in rebase Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: Torkel Ödegaard <torkel@grafana.com>
This commit is contained in:
Christopher Moyer
co-authored by
Torkel Ödegaard
Jack Baldry
Torkel Ödegaard
Jack Baldry
parent
104c4a7630
commit
a568d421f8
@@ -21,13 +21,13 @@ If you encounter an error or problem, then you can check the Grafana server log.
|
||||
|
||||
You can enable more logging by changing log level in the Grafana configuration file.
|
||||
|
||||
For more information, refer to [Enable debug logging in Grafana CLI]({{< relref "../administration/cli.md#enable-debug-logging" >}}) and the [log section in Configuration]({{< relref "../administration/configuration.md#log" >}}).
|
||||
For more information, refer to [Enable debug logging in Grafana CLI]({{< relref "../administration/cli/#enable-debug-logging" >}}) and the [log section in Configuration]({{< relref "../setup-grafana/configure-grafana/#log" >}}).
|
||||
|
||||
## Troubleshoot transformations
|
||||
|
||||
Order of transformations matters. If the final data output from multiple transformations looks wrong, try changing the transformation order. Each transformation transforms data returned by the previous transformation, not the original raw data.
|
||||
|
||||
For more information, refer to [Debug a transformation]({{< relref "../panels/transform-data/debug-transformation.md" >}}).
|
||||
For more information, refer to [Debug a transformation]({{< relref "../panels/transform-data/debug-transformation/" >}}).
|
||||
|
||||
## Text missing with server-side image rendering (RPM-based Linux)
|
||||
|
||||
|
||||
@@ -1,58 +0,0 @@
|
||||
---
|
||||
aliases:
|
||||
- /docs/grafana/latest/troubleshooting/diagnostics/
|
||||
title: Enable diagnostics
|
||||
weight: 200
|
||||
---
|
||||
|
||||
# Enable diagnostics
|
||||
|
||||
You can set up the `grafana-server` process to enable certain diagnostics when it starts. This can be helpful
|
||||
when investigating certain performance problems. It's _not_ recommended to have these enabled by default.
|
||||
|
||||
## Turn on profiling
|
||||
|
||||
The `grafana-server` can be started with the arguments `-profile` to enable profiling, `-profile-addr` to override the default HTTP address (`localhost`), and
|
||||
`-profile-port` to override the default HTTP port (`6060`) where the `pprof` debugging endpoints are available. For example:
|
||||
|
||||
```bash
|
||||
./grafana-server -profile -profile-addr=0.0.0.0 -profile-port=8080
|
||||
```
|
||||
|
||||
Note that `pprof` debugging endpoints are served on a different port than the Grafana HTTP server.
|
||||
|
||||
You can configure or override profiling settings using environment variables:
|
||||
|
||||
```bash
|
||||
export GF_DIAGNOSTICS_PROFILING_ENABLED=true
|
||||
export GF_DIAGNOSTICS_PROFILING_ADDR=0.0.0.0
|
||||
export GF_DIAGNOSTICS_PROFILING_PORT=8080
|
||||
```
|
||||
|
||||
Refer to [Go command pprof](https://golang.org/cmd/pprof/) for more information about how to collect and analyze profiling data.
|
||||
|
||||
## Use tracing
|
||||
|
||||
The `grafana-server` can be started with the arguments `-tracing` to enable tracing and `-tracing-file` to override the default trace file (`trace.out`) where trace result is written to. For example:
|
||||
|
||||
```bash
|
||||
./grafana-server -tracing -tracing-file=/tmp/trace.out
|
||||
```
|
||||
|
||||
You can configure or override profiling settings using environment variables:
|
||||
|
||||
```bash
|
||||
export GF_DIAGNOSTICS_TRACING_ENABLED=true
|
||||
export GF_DIAGNOSTICS_TRACING_FILE=/tmp/trace.out
|
||||
```
|
||||
|
||||
View the trace in a web browser (Go required to be installed):
|
||||
|
||||
```bash
|
||||
go tool trace <trace file>
|
||||
2019/11/24 22:20:42 Parsing trace...
|
||||
2019/11/24 22:20:42 Splitting trace...
|
||||
2019/11/24 22:20:42 Opening browser. Trace viewer is listening on http://127.0.0.1:39735
|
||||
```
|
||||
|
||||
For more information about how to analyze trace files, refer to [Go command trace](https://golang.org/cmd/trace/).
|
||||
@@ -26,7 +26,7 @@ The most common problems are related to the query and response from your data so
|
||||
like a bug or visualization issue in Grafana, it is almost always a problem with the data source query or
|
||||
the data source response. Start by inspecting your panel query and response.
|
||||
|
||||
For more information, refer to [Inspect request and response data]({{< relref "../panels/query-a-data-source/inspect-request-and-response-data.md" >}}).
|
||||
For more information, refer to [Inspect request and response data]({{< relref "../panels/query-a-data-source/inspect-request-and-response-data/" >}}).
|
||||
|
||||
## My query is slow
|
||||
|
||||
|
||||
Reference in New Issue
Block a user