Mirrors/dokku
1
0
Fork 0
mirror of https://github.com/dokku/dokku.git synced 2025-12-29 00:25:08 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix: ensure the vector container does not exit when no configured sinks are in place

Browse Source
This commit is contained in:
Jose Diaz-Gonzalez
2021-01-04 01:12:25 -05:00
parent 43d6a2ad94
commit 94696e81fa
3 changed files with 27 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/deployment/logs.md
View File

@@ -73,8 +73,6 @@ dokku logs:vector-start
This will start a new container named `vector` with Dokku's vector config mounted and ready for use. If a running container already exists, this command will do nothing. Additionally, if a container exists but is not running, this command will attempt to start the container.
By default, the vector container will do nothing and may exit immediately. It is necessary to configure a sink in order to ensure the vector container runs as necessary.
While the default vector image is hardcoded, users may specify an alternative via the `--vector-image` flag:
```shell
@@ -101,8 +99,6 @@ The `vector` container will be stopped and removed from the system. If the conta
#### Configuring a log sink
> If no sinks are specified, the vector container will exit.
Vector uses the concept of log "sinks" to send logs to a given endpoint. Log sinks may be configured globally or on a per-app basis by specifying a `sink` in DSN form with the `logs:set` command. Specifying a sink value will reload any running vector container.
```shell
@@ -131,8 +127,6 @@ As with app-specific sink settings, the global value may also be cleared by sett
dokku logs:set --global sink
```
If no sink is specified, the vector container may exit prematurely.
##### Log Sink DSN Format
The DSN form of a sink is as follows: