screenshot-service.properties Properties
The following table lists properties you might adjust for the Composer Screenshot microservice.
For information on editing configuration files, see Edit a Composer Configuration File.
Property Name | Default Value | Description |
---|---|---|
pool.queue.size | 10 | Sets the queue size for Screenshot microservice requests. This property and the pool.thread.size property specify the upper limits for Screenshot microservice processing. When the number of screenshot requests exceeds the limits set by these two properties, you will receive HTTP 429 "Too Many Requests" errors. You can exceed these limits in a number of ways, including:
You can increase the values of this property and the pool.thread.size property when you encounter too many failed screenshots. However, do so with caution. |
pool.thread.size | 20 | Sets the thread count for Screenshot microservice requests. This property and the pool.queue.size property specify the upper limits for Screenshot microservice processing. When the number of screenshot requests exceeds the limits set by these two properties, you will receive HTTP 429 "Too Many Requests" errors. You can exceed these limits in a number of ways, including:
If your use of Composer includes scheduling dashboard reports, update this setting so it is greater than the number of concurrent reports. You can also increase the values of this property and the pool.queue.size property when you encounter too many failed screenshots. However, do so with caution. |
syslog.host | 127.0.0.1 |
Sets the host IP address for Syslog server message logging.
Example:
|
syslog.log.level | OFF |
Sets the syslog log level for messages logged to the Syslog server. The following options are available for this property:
TRACE, DEBUG, INFO, WARN, and ERROR.
Example: |
syslog.port | 1514 |
Sets the port for Syslog server message logging.
Example:
|
syslog.suffix | local |
Specifies a suffix that is appended at the end of the Syslog server log entry that Composer generates.
Example:
|
Comments
0 comments
Please sign in to leave a comment.