Merge branch 'master' of https://github.com/getsentry/sentry-docs into revert-12296-aliu/unpublish-unleash

Author: aliu39

develop-docs/sdk/expected-features/index.mdx

@@ -225,7 +225,7 @@ Whenever possible, avoid adding the attachment altogether if taking the screensh
 
 ## Before-Send Hook
 
-Hook called with the event (and on some platforms the hint) that allows the user to decide whether an event should be sent or not.  This can also be used to further modify the event. This only works for `error` events. For `transactions` it is recommended to have `beforeSendTransaction` implemented in SDKs.
+Hook called with the event (and on some platforms the hint) that allows the user to decide whether an event should be sent or not.  This can also be used to further modify the event. This only works for `error` events. For `transactions` it is recommended to have `beforeSendTransaction` implemented in SDKs. To understand when you should call this in your SDK, please refer to the [error filter ordering of sessions](/sdk/telemetry/sessions/#filter-order).
 
 ## Before-Breadcrumb Hook
 

develop-docs/sdk/telemetry/traces/index.mdx

@@ -236,7 +236,7 @@ The random value is set according to the following rules:
 2. It is _recommended_ to generate the random number deterministically using the trace ID as seed or source of randomness. The exact method by which the random number is created is implementation defined and may vary between SDK implementations. See 4. on why this behaviour is desirable.
 3. On incoming traces, an SDK assumes the `sample_rand` value along with the rest of the DSC, overriding an existing value if needed.
 4. If `sample_rand` is missing on an incoming trace, the SDK creates and from now on propagates a new random number on-the-fly, based on the following rules:
-   1. If `sample_rate` and `sampled` are propgated, create `sample_rand` so that it adheres to the invariant. This means, for a decision of `True` generate a random number in half-open range `[0, rate)` and for a decision of `False` generate a random number in range `[rate, 1]`.
+   1. If `sample_rate` and the sampling decision (from the `sentry-trace` header) are propgated, create `sample_rand` so that it adheres to the invariant. This means, for a decision of `True` generate a random number in half-open range `[0, rate)` and for a decision of `False` generate a random number in range `[rate, 1]`.
    2. If the sampling decision is missing, generate a random number in range of `[0, 1)` (including 0.0, excluding 1.0), like for a new trace.
 
 The SDK should always use the stored random number (`sentry-sample_rand`) for sampling decisions and should no longer rely on `math.random()` or similar functions in tracing code:

develop-docs/self-hosted/index.mdx

@@ -123,7 +123,7 @@ To apply new Docker daemon configuration, restart your Docker service with `syst
 
 <Alert title="Note" level="info">
   The value `172.17.0.0/16` is the default IP pools for Docker. If you are customizing your Docker default IP pools, please modify the value accordingly.
-  Further information regarding Docker default IP pools can be found on the [Troubleshooting guide](/self-hosted/troubleshooting/#docker-network-conflicting-ip-address).
+  Further information regarding Docker default IP pools can be found on the [Troubleshooting guide](/self-hosted/troubleshooting/docker/#docker-network-conflicting-ip-address).
 </Alert>
 
 ## Configuration

develop-docs/self-hosted/troubleshooting.mdx

@@ -0,0 +1,83 @@
+---
+title: Troubleshooting Docker
+sidebar_title: Docker
+sidebar_order: 3
+---
+
+## Container Healthcheck
+
+There may be some circumstances which you may want to increase or decrease healthcheck interval, timeout or retries for your custom needs. This can be achieved by editing `HEALTHCHECK_INTERVAL`, `HEALTHCHECK_TIMEOUT`, `HEALTHCHECK_RETRIES` variables' values in `.env`.
+
+Occasionally, you might see an error like this
+```
+container for service "${servicename}" is unhealthy
+```
+
+This can usually be resolved by running `docker compose down` and `docker compose up --wait` or rerunning the install script.
+
+## Docker Network Conflicting IP Address
+
+Self-hosted Sentry is using Docker's bridge networking, in which use a specific private IP range. By default, Docker uses `172.17.0.0/16` range (`172.17.0.0`-`172.17.255.255`). This may cause conflict with your private network. You can change Docker's default IP range by configuring the `/etc/docker/daemon.json` file. If the file does not exists, you can create it yourself.
+
+Assuming your safe IP range is `10.147.0.0/16` and `10.146.0.0/16`, your configuration would be:
+
+```json
+{
+    "default-address-pools": [
+   {
+     "base": "10.147.0.0/16",
+     "size": 24
+   },
+   {
+     "base": "10.146.0.0/16",
+     "size": 24
+   }
+ ]
+}
+```
+
+To apply new Docker daemon configuration, restart your Docker service with `systemctl restart docker`.
+
+Make sure you are using [valid private IP ranges](https://en.wikipedia.org/wiki/Reserved_IP_addresses), that is between these ranges:
+- `10.0.0.0/8` (address range of `10.0.0.0`–`10.255.255.255`)
+- `100.64.0.0/10` (address range of `100.64.0.0`–`100.127.255.255`)
+- `172.16.0.0/12` (address range of `172.16.0.0`–`172.31.255.255`)
+- `192.0.0.0/24` (address range of `192.0.0.0`–`192.0.0.255`)
+- `192.168.0.0/16` (address range of `192.168.0.0`–`192.168.255.255`)
+- `198.18.0.0/15` (address range of `198.18.0.0`–`198.19.255.255`)
+
+For further reading, you can see Matthew Stratiotto's article on [The definitive guide to docker's default-address-pools option](https://straz.to/2021-09-08-docker-address-pools/).
+
+## Logs Disk Usage
+
+If you are suspecting persisted logs from Docker container logs consumes a lot of your disk space, you can configure the amount of persisted logs on Docker by configuring the `/etc/docker/daemon.json` file. If the file does not exists, you can create it yourself.
+
+```json
+{
+  "log-driver": "local",
+  "log-opts": {"max-size": "10m", "max-file": "3"}
+}
+```
+
+To apply new Docker daemon configuration, restart your Docker service with `systemctl restart docker`.
+
+If you want to delete immediate Docker logs, you can execute this as `root` user:
+
+```shell
+truncate -s 0 /var/lib/docker/containers/**/*-json.log
+```
+
+## Image and Builder Cleanup
+
+Executing `./install.sh` will build a new Sentry Docker container, executing it often might cause Docker to consume your disk space. You can safely prune old or unneeded Docker containers, image, or builder to re-acquire used disk space. Executing these will not affect current running containers and volumes.
+
+```shell
+docker container prune
+docker builder prune
+docker image prune --all
+# WARNING: Executing "volume prune" might delete `sentry-vroom` volume as it's not an external volume.
+docker volume prune
+docker network prune
+```
+
+Append `-f` flag for no confirmation on deletions.