...
Respond with POST data and triggered action(s) to the client
Controls if the inbound incoming end point shall return what rule was triggered or just 200 OK
...
then if an event occurs it will log on both actions if the JQL was met or not.
...
This setting controls how many worker threads iHub will use to process the queue of requests. Default is 2. Consider increase this number if there is a lot of calls and long running calls.
Each node in a Jira datacenter setup will have the numbers specified, so if you run 4 nodes, the default is 2 x 4 = 8 worker threads in totoal.
Log retention setting
By default the log retention is Off, specifying 0 (zero) as the number will turn the log retention off.
...
What should I do if I want to keep the logs longer without using the database? Use the log appender properties to save the execution log and incoming log to files, backup these files to a storage area or read them into a log management too. Read more how to set this up here iHub Logging
Proxy Settings
Disabled by default. If the Jira server is behind firewalls and do not have internet access except by using a proxy, then use these settings to tell iHub what proxy to use.
Proxy Port | Port on which the proxy listen to |
|---|---|
Proxy Host | The address to the proxy server, could be IP or hostname |
Non-Proxy Hosts | Define a pattern when to not use a proxy, e.g. localhost | *rixter.se |
Pagination settings
This setting controls how many iterations iHub maxium can do, this is to prevent infinity loops if the action is configured wrongly or API returns an endless loop of arrays.
Default is 150, meaning it will make 150 request and if more is in the queue it will stop and give an error in the Execution log.
Mutual TLS Settings
Setting will tell iHub what keystore and password to use for Mutual TLS. See more on how to TLS and Certificates for guides.
Mutual TLS will try to load the default keystore if no settings is applied. It will also try to use the paths from the java params below.
...