proxy.golang.org : github.com/adirelle/bilies-go
Batchs Messages are gathered in batchs before being sent to the server. Batchs are sent when the number of messages reachs a defined value or when the delay since the last sent exceeds a defined value. The following switches control the generation of bulk messages: Internal logging (i.e. messages generated by bilies-go) is done asynchronously. By default, messages of level NOTICE and higher are written do the standard error. The following switches control logging: Sending HUP to bilies-go causes the logfile to be reopened. PID file bilies-go collects several metrics. They can be written to the log by sending an USR1 signal to the process. Several hosts can be passed on the command line to create a backend pool. When a network error occurs while tryng to reach a backend, it is temporarily removed from the pool, using a delay which exponentially increases on consecutive errors. This delay starts at 500ms and is capped at 2 minutes. Incoming messages are enqueued into LevelDB database. The following switch control queueing: bilies-go waits for JSON messages on its standard input. They should have the following format: The "id" is optional; if missing, a time-based UUID is generated. It is used to identify the document in ElasticSearch. Invalid messages are ignored and logged. bilies-go expects UTF-8 messages (as JSON). In case the input is not a valid UTF-8 strings, a charset conversion is tried. The following switch controls input reading: bilies-go retries the requests indefinitively on network or 5xx errors. In case of 400 error, batchs are split in smaller parts and send independently to find the culprit. The following switchs control requests:
Registry
-
Source
- Documentation
- JSON
purl: pkg:golang/github.com/adirelle/bilies-go
License: GPL-3.0
Latest release: over 8 years ago
First release: over 8 years ago
Namespace: github.com/adirelle
Stars: 0 on GitHub
Forks: 0 on GitHub
See more repository details: repos.ecosyste.ms
Last synced: 23 days ago