Adapter Advanced Settings
- 5 minutes to read
In addition to the adapter connection configuration settings, each adapter has Advanced Settings used to support your use of Axonius.
To configure the adapter Advanced Settings, do the following:
- Open the Adapters screen. Click the icon on the left navigation panel.
- Search and click the relevant adapter. The Adapter Connections screen opens displaying the list of connected connections.
- Click Advanced Settings. The adapter advanced settings pane appears, displaying the Adapter Configuration tab.
- To save any configuration changes, click Save Config.
You can control and configure the following settings:
|Setting Name||What is it?||Why Do you Need it?||Example|
|Do not fetch device if not seen by source in last X hours||If selected, Axonius will only fetch device information if that device has been seen by the adapter connection ('Last Seen' field) within in the last specified number of hours.
If no value is configured, Axonius will always fetch device information.
The default value for this setting is 2160 hours (90 days).
|This setting allows you to avoid fetching old devices that are no longer part of your network, but still exist in the data repository of the adapter connection.||If the value is 2160 hours, any device which has not been seen by the adapter connection in the last five years will not be pulled into Axonius.|
|Delete device if not fetched from source in last X hours||If selected, Axonius will delete the device data fetched from the adapter connection if the device has not been fetched from that adapter connection in the last specified number of hours. Axonius will delete only the information fetched from that specific adapter, keeping the rest of the device information (if exists) intact.
If no value is configured, Axonius never deletes device information.
The default value for this setting is 48 hours.
|This setting allows you to avoid keeping data for devices that no longer exist on the ‘source’, under the assumption that if a device has not been fetched from an adapter connection, it is no longer exists, and can be deleted.||If the value is 48 hours, Axonius will delete a device if it has not been fetched from the adapter connection in 2 days.|
|Do not fetch user if not seen by source in last X hours||If selected, this is the same as the “Do not fetch device if not seen by source in last X hours” setting, but in the context of user information.
The default value for this field is empty, meaning, Axonius always fetches user assets data.
|Delete user if not fetched from source in last X hours||If selected, this is the same as the same as the “Delete device if not fetched from source in last X hours” setting, but in the context of user information.
By default, this setting is not in use.
|Minimum hours to wait before next discovery cycle for this adapter||The minimum number of hours before initiating the next adapter discovery cycle.
If no value is configured, the adapter discovery cycle will be always part of the global discovery cycle.
By default, this setting is not in use.
|It enables scheduling a specific adapter discovery cycle that runs longer than the global discovery cycle.||If the value is 2 hours and the global discovery starts every 1 hour, then Axonius will pull data from the adapter every 2 hours instead of every 1 hour.|
|Adapter connection timeout in seconds||The number of seconds before the attempt to connect to the adapter connection is considered to be timed out.
If the connection has failed, an error icon will be displayed next to the adapter connection icon.
If no value is configured, there will be no connection timeout. It is not recommended to leave this option blank.
The default value for this setting is 300 seconds (five minutes).
For more details, see Connecting Adapters.
|It enables avoiding endless connection attempts when the connection is down.||If the value is 300 seconds, as part of discovery cycle, if Axonius fails to connect the adapter connection after 300 seconds, the connection is considered to be failed, and an error icon will be displayed next to the adapter connection icon. Axonius will then continue the discovery cycle and will try to connect the next adapter connection.|
|Entity fetching timeout in seconds||The number of seconds passed from the last data fetched during the discovery cycle.
This configuration determines when Axonius will stop fetching data from the adapter connection if issues are identified during the discovery process.
If no value is set, there will be no timeout. It is not recommended to leave this option blank.
The default value for this setting is 5400 seconds (90 minutes).
|It enables avoiding endless data fetching attempts when there is any error during the process.||If the value is 5400 seconds (90 minutes), a discovery cycle has been started, connection with the adapter connection has been established, and data fetching has started. If Axonius identifies an issue with fetching the data and no new data is retrieved for over 90 minutes, Axonius will terminate the transaction and will continue to the next one.|
|Discard entity data if 'Last Seen' fetched is older than 'Last Seen' saved||If selected, Axonius will ignore older device or user data (based on fetched ‘Last Seen’ field) when data for a specific device or user is received from several adapter connections of the same adapter type.
The default value for this field is empty.
|In some cases, Axonius may fetch device information from several different adapter connections of the same adapter type. The device information each of those sources holds may be different due to the last time the device information was updated in that adapter connection ('Last Seen' field).||For example, if a device named 'Device123' information is fetched from two adapters connections.
'Last Seen' fetched is: from server1 - Jan-1-2019. From server2 - Jan-5-2019.
Therefore, if set, Axonius will discard and ignore the data fetched from server1.
|Run as a real-time adapter||If selected, Axonius will pull information from the adapter constantly. This means that once Axonius completes the discovery cycle for the adapter connection, it will initiate another cycle immediately, and so on.
Notice that if 'Minimum time to initiate next entities fetch' is configured, the ‘Run as a real-time adapter’ setting will be ignored, and the next discovery cycle will start based on the 'Minimum time to initiate next entities fetch' setting.
By default, for most adapters, this setting is not in use.
|If the adapter’s collected data is updated in very short cycles (seconds or minutes), use this setting to make sure the fetched data is always up to date.|