The bing.ini config file, located at /etc/squirro/bing.ini configures the workings of the Bing Provider.
Table of Contents
API Key
The Bing API key needs to be requested directly from Microsoft on the Azure Marketplace. It can then be configured in the section bing.
| Key | Usage | Default |
|---|---|---|
| account_key | The Bing News API key. | (No default value) |
| root_url | API endpoint for the Bing News API. | https://api.datamarket.azure.com/Bing/Search/ |
Source Manager
The source manager implements the polling behavior. The behavior is configured in the two sections source_manager and source_manager_web (for news and web sources respectively) with the following keys.
All values are JSON-encoded time delta objects and can contain the keys seconds, minutes, hours, days, weeks.
| Key | Usage | Default for News |
|---|---|---|
check_delay | How long after errors the source is polled again. The delay is exponentially increased with each error. |
|
max_error_delay | The maximum delay after errors. | {"days": 3} |
success_delay | Delay when the Bing API request succeeded. When no new items were found, this interval is increased with each request. This ensures that sources with very low result frequency don't use up too much of the API quota. | {"minutes": 15} |
max_success_delay | The maximum delay when no new items were found. |
|
To avoid thundering herd problems, there is some randomness applied to these values (+/- one fourth of the delay).
Example Configuration
[source_manager]
check_delay = {"minutes": 1}
max_error_delay = {"days": 3}
success_delay = {"minutes": 15}
max_success_delay = {"hours": 12}
[source_manager_web]
check_delay = {"days": 1}
max_error_delay = {"days": 7}
success_delay = {"days": 1}
max_success_delay = {"days": 3}