We use a piece of software called Collector Server to host and manage all our available collectors. To enable the collector for a customer: In the Collector Server GUI, access the domain in which you want this instance to be created Click Add Collector and find the one you wish to add. In the Version field, select the latest value. In the Collector Name field, set the value you prefer (this name must be unique inside the same Collector Server domain). In the sending method select Direct Send. Direct Send configuration is optional for collectors that create Table events, but mandatory for those that create Lookups. In the Parameters section, establish the Collector Parameters as follows below:
Editing the JSON configuration| Code Block |
|---|
{
"global_overrides": {
"debug": False
},
"inputs": {
"automox": {
"id": "<short_unique_id>",
"enabled": <input_status>,
"credentials": {
"api_key": "<api_key>",
"organization_id": "<organization_id>"
},
"services": {
"all_packages_for_all_devices": {
"request_period_in_seconds": <request_period_in_seconds>,
"override_tag": "<custom_devo_tag>",
"override_include_unmanaged": "<override_include_unmanaged>",
"override_awaiting": "<override_awaiting>",
"override_page_size": "<override_page_size>"
},
"software_packages_by_device_id": {
"device_id": "<device_id>",
"request_period_in_seconds": <request_period_in_seconds>,
"override_tag": "<custom_devo_tag>",
"override_page_size": "<override_page_size>"
}
}
}
}
} |
| Info |
|---|
All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the services object. |
Please replace the placeholders with real world values following the description table below: Parameter | Data Type | Type | Value Range / Format | Details | input_id
| int
| Mandatory
| Minimum length: 1
Maximum length: 5 | Use this param to give an unique id to this input service. | Note |
|---|
This parameter is used to build the persistence address, do not use the same value for multiple collectors. It could cause a collision. |
| input_status
| bool
| Mandatory
| false / true
| If the value is true, the input definition will be executed. If the value is false, the service will be ignored. | api_key
| str
| Mandatory
| Minimum length: 1 | api_key of the Automox server | organization_id
| int
| Mandatory
| Minimum length: 1 | organization_id of the Automox server
| request_period_in_seconds
| int
| Optional
| Minimum length: 1 | Period in seconds used between each data pulling, this value will overwrite the default value (300 seconds) This parameter can be removed or commented. | custom_devo_tag
| str
| Optional
| A Devo Tag. For more information see Devo Tags. | This parameter allows to define a custom devo tag. This parameter can be removed or commented. | override_include_unmanaged
| int
| optional
| Enum: 0 1 | Include applications Automox does not currently support for patching. This parameter can be removed or commented. | override_awaiting
| int
| optional
| Enum: 0 1 | Filter based installation status of package. awaiting=1: Packages that are currently available but not installed. awaiting=0: Packages that are already installed. This parameter can be removed or commented. | override_page_size
| int
| optional
| Minimum length: 1 | A limit on the number of results to be returned, between 1 and 500, with a default of 500. This parameter can be removed or commented. |
| Rw tab |
|---|
| title | On-premise collector |
|---|
|
This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure should be created for being used when running the collector: | Code Block |
|---|
<any_directory>
└── devo-collectors/
└── <product_name>/
├── certs/
│ ├── chain.crt
│ ├── <your_domain>.key
│ └── <your_domain>.crt
├── state/
└── config/
└── config.yaml |
| Note |
|---|
Replace <product_name> with the proper value. |
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in <product_name>/certs/. Learn more about security credentials in Devo here.  Image Removed Image Added| Note |
|---|
Replace <product_name> with the proper value. |
Editing the config.yaml file| Code Block |
|---|
globals:
debug: False
id: <collector_id>
name: <collector_name>
persistence:
type: filesystem
config:
directory_name: state
outputs:
devo_1:
type: devo_platform
config:
address: <devo_address>
port: 443
type: SSL
chain: <chain_filename>
cert: <cert_filename>
key: <key_filename>
inputs:
automox:
id: <input_id>
enabled: <input_status>
credentials:
api_key: <api_key>
organization_id: <organization_id>
services:
all_packages_for_all_devices:
request_period_in_seconds: <request_period_in_seconds>
override_tag: <custom_devo_tag>
override_include_unmanaged: <override_include_unmanaged>
override_awaiting: <override_awaiting>
override_page_size: <override_page_size>
software_packages_by_device_id:
device_id: <device_id>
request_period_in_seconds: <request_period_in_seconds>
override_tag: <custom_devo_tag>
override_page_size: <override_page_size> |
| Info |
|---|
All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the services object. |
Replace the placeholders with your required values following the description table below: Parameter | Data type | Type | Value range / Format | Details |
|---|
collector_id
| int
| Mandatory
| Minimum length: 1
Maximum length: 5 | Use this param to give an unique id to this collector. | collector_name
| str
| Mandatory
| Minimum length: 1
Maximum length: 10 | Use this param to give a valid name to this collector. | devo_address
| str
| Mandatory
| collector-us.devo.io
collector-eu.devo.io
| Use this param to identify the Devo Cloud where the events will be sent. | chain_filename
| str
| Mandatory
| Minimum length: 4
Maximum length: 20 | Use this param to identify the chain.cert file downloaded from your Devo domain. Usually this file's name is: chain.crt | cert_filename
| str
| Mandatory
| Minimum length: 4
Maximum length: 20 | Use this param to identify the file.cert downloaded from your Devo domain. | key_filename
| str
| Mandatory
| Minimum length: 4
Maximum length: 20 | Use this param to identify the file.key downloaded from your Devo domain. | input_id
| int
| Mandatory
| Minimum length: 1
Maximum length: 5 | Use this param to give an unique id to this input service. | Note |
|---|
This parameter is used to build the persistence address, do not use the same value for multiple collectors. It could cause a collision. |
| input_status
| bool
| Mandatory
| false / true
| If the value is true, the input definition will be executed. If the value is false, the service will be ignored. | api_key
| str
| Mandatory
| Minimum length: 1 | api_key of the Automox server | organization_id
| int
| Mandatory
| Minimum length: 1 | organization_id of the Automox server
| request_period_in_seconds
| int
| Optional
| Minimum length: 1 | Period in seconds used between each data pulling, this value will overwrite the default value (300 seconds) This parameter can be removed or commented. | custom_devo_tag
| str
| Optional
| A Devo Tag. For more information see Devo Tags. | This parameter allows to define a custom devo tag. This parameter can be removed or commented. | override_include_unmanaged
| int
| optional
| Enum: 0 1 | Include applications Automox does not currently support for patching. This parameter can be removed or commented. | override_awaiting
| int
| optional
| Enum: 0 1 | Filter based installation status of package. awaiting=1: Packages that are currently available but not installed. awaiting=0: Packages that are already installed. This parameter can be removed or commented. | override_page_size
| int
| optional
| Minimum length: 1 | A limit on the number of results to be returned, between 1 and 500, with a default of 500. This parameter can be removed or commented. |
Download the Docker imageThe collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table: Use the following command to add the Docker image to the system: | Code Block |
|---|
gunzip -c <image_file>-<version>.tgz | docker load |
| Note |
|---|
Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace <image_file> and <version> with a proper value. |
The Docker image can be deployed on the following services: DockerExecute the following command on the root directory <any_directory>/devo-collectors/<product_name>/ | Code Block |
|---|
docker run
--name collector-<product_name>
--volume $PWD/certs:/devo-collector/certs
--volume $PWD/config:/devo-collector/config
--volume $PWD/state:/devo-collector/state
--env CONFIG_FILE=config.yaml
--restart=always
--interactive
--tty
<image_name>:<version> |
| Note |
|---|
Replace <product_name>, <image_name> and <version> with the proper values. |
Docker ComposeThe following Docker Compose file can be used to execute the Docker container. It must be created in the <any_directory>/devo-collectors/<product_name>/ directory. | Code Block |
|---|
version: '3'
services:
collector-<product_name>:
image: <image_name>:${IMAGE_VERSION:-latest}
container_name: collector-<product_name>
restart: always
volumes:
- ./certs:/devo-collector/certs
- ./config:/devo-collector/config
- ./credentials:/devo-collector/credentials
- ./state:/devo-collector/state
environment:
- CONFIG_FILE=${CONFIG_FILE:-config.yaml} |
To run the container using docker-compose, execute the following command from the <any_directory>/devo-collectors/<product_name>/ directory: | Code Block |
|---|
IMAGE_VERSION=<version> docker-compose up -d |
| Note |
|---|
Replace <product_name>, <image_name> and <version> with the proper values. |
We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration. | 
