Update documentation for self-hosting OneUptime with clearer endpoint examples

This commit is contained in:
Simon Larsen 2024-11-06 11:41:41 +00:00
parent 6286653dd4
commit 7fd0000c68
No known key found for this signature in database
GPG Key ID: 96C5DCA24769DBCA
2 changed files with 5 additions and 2 deletions

View File

@ -109,7 +109,7 @@ An example of full configuration file is shown below:
</match> </match>
``` ```
**If you're self hosting OneUptime**: If you're self hosting OneUptime you can replace the `endpoint_url` with the URL of your OneUptime instance. `http(s)://<YOUR_HOST>/fluentd/logs` **If you're self hosting OneUptime**: If you're self hosting OneUptime you can replace the `endpoint_url` with the URL of your OneUptime instance. `http(s)://YOUR_ONEUPTIME_HOST/fluentd/logs`
## Usage ## Usage

View File

@ -55,7 +55,10 @@ export OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.oneuptime.com
export OTEL_SERVICE_NAME=my-service export OTEL_SERVICE_NAME=my-service
``` ```
If you're self-hosting oneuptime, this can be changed to your self hosted OpenTelemetry collector endpoint (eg: `http(s)://<your-oneuptime-host>/otlp`)
**Self Hosted OneUptime**
If you're self-hosting oneuptime, this can be changed to your self hosted OpenTelemetry collector endpoint (eg: `http(s)://YOUR-ONEUPTIME-HOST/otlp`)
Once you run your application, you should see the logs in the OneUptime telemetry service page. Please contact support@oneuptime.com if you need any help. Once you run your application, you should see the logs in the OneUptime telemetry service page. Please contact support@oneuptime.com if you need any help.