Bolt
Why do I see unusual 429 HTTP errors?
All our Bolts are equipped with a request limiter to limit incoming concurrent requests. If you hit this limiter you’re likely sending out too many requests from the same session ID, at the same time.
We’ve implemented this to ensure a stable platform for your Bolts to run off. A lot of concurrent requests can severely degrade your Bolts performance, leading to longer loading times.
If you see this error and don’t know what to do, contact our Support at servebolt.com. We can help you find out what requests are causing this behavior and what you can do to prevent it from happening.
What structure do your log files have?
At Servebolt our log files are written in a custom format. This makes some analytics programs not able to read them right away. In most cases, you’ll need to provide the format we use.
For access logs, the following format is used:
LogFormat "%a PID:%P EID:%L U:%u %t %{HOST}i \"%r\" %>s %B IN:%I OUT:%O %{ms}Tms \"%{Referer}i\" \"%{User-Agent}i\" ct:%{Content-Type}o"And for our error logs, we use this format:
ErrorLogFormat "[%-t] [PID:%-P EID:%-L] [%-m:%-l:%-F] [Host:%-{HOST}i Client:%-a] %E %-M"