Adapter Advanced Settings
  • 6 minutes to read
  • Print
  • Share
  • Dark
    Light

Adapter Advanced Settings

  • Print
  • Share
  • Dark
    Light

While the adapter connection configuration settings are specific for each of the adapter's connections, each adapter has Advanced Settings that applies for all the adapter's connections.

NOTE
Some adapters, for example, Amazon Web Services (AWS) and Microsoft Active Directory (AD), have adapter specific advanced settings, that are displayed under a separate tab in the Advanced Settings pane.

image.png

To configure the adapter Advanced Settings, do the following:

  1. Open the Adapters page. Click the image.png icon on the left navigation panel.
  2. Search and click the relevant adapter. The Adapter Connections page opens displaying the list of connected connections.
  3. Click Advanced Settings. The adapter advanced settings pane appears, displaying the Adapter Configuration tab.
  4. To save any configuration changes, click Save Config.



You can control and configure the following settings:

  1. Ignore devices that have not been seen by the source in the last X hours
  2. Delete devices that have not been returned from the source in the last X hours
  3. Ignore users that have not been seen by the source in the last X hours
  4. Delete users that have not been returned from the source in the last X hours
  5. Override the global discovery schedule for this adapter to wait X hours before fetching
  6. Wait for a connection to the source for up to X seconds
  7. Wait for a response from the source for up to X seconds
  8. Ignore matching assets from the source if a subsequent asset was seen by the source before the previously fetched asset
  9. Enable real-time adapter (ignores all discovery cycle settings and continuously repeats fetches from the source)

Ignore devices that have not been seen by the source in the last X hours

This setting lets you avoid fetching old devices that are no longer part of your network, but that still exist in the data repository of the adapter connection.

  • If supplied, all connections for the adapter will only fetch device information if that device asset entity has been seen by the adapter connection ('Last Seen' field) within in the last specified number of hours.
  • If not supplied, all connections for the adapter will always fetch device information.

For example, if the value is 2160 hours, any device asset entity which has not been seen by the adapter connection in the last 90 days will not be pulled into Axonius.

Delete devices that have not been returned from the source in the last X hours

This setting lets you avoid keeping data for devices that no longer exist on the ‘source’, under the assumption that if a device asset entity has not been fetched from an adapter connection, it no longer exists and can be deleted.

  • If supplied, all connections for the adapter will delete the device data fetched from the source if the device asset entity has not been fetched from that adapter connection (source) in the last specified number of hours. Only the information fetched from that specific adapter will be deleted, keeping the rest of the device information (if exists) intact.
  • If not supplied, all connections for the adapter will never delete device information.

For example, if the value is 48 hours, a device asset entity will be deleted if it has not been fetched from the adapter connection in 2 days.

Ignore users that have not been seen by the source in the last X hours

This setting is the same as the Ignore devices that have not been seen by the source in the last X hours setting, but in the context of user information.

Delete users that have not been returned from the source in the last X hours

This setting is the same as the Delete devices that have not been returned from the source in the last X hours setting, but in the context of user information.

Override the global discovery schedule for this adapter to wait X hours before fetching

This setting lets you schedule a specific adapter discovery cycle that runs longer than the global discovery cycle.

  • If supplied, Axonius will wait for the minimum number of hours specified before initiating the next adapter discovery cycle.
  • If not supplied, the adapter discovery cycle will be always part of the global discovery

For example, 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.

Wait for a connection to the source for up to X seconds

This setting lets you avoid endless connection attempts when the connection is down.

  • If supplied, all connections for the adapter will wait for the specified 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 not supplied, all connections for the adapter will not have any connection timeout.
NOTE

It is not recommended to leave this option blank.

For example, if the value is 300 seconds, as part of discovery cycle, Axonius will display an error icon next to the adapter connection if a connection has not been established within 300 seconds. Axonius will then continue the discovery cycle and will try to connect the next adapter connection.

Wait for a response from the source for up to X seconds

This setting lets you avoid endless data fetching attempts when there is any error during the process. This setting determines when Axonius will stop fetching data from the adapter connection if issues are identified during the discovery process.

  • If supplied, all connections for the adapter will wait for the specified number of seconds passed from the last data fetched during the discovery cycle.
  • If not supplied, all connections for the adapter will not have any timeout.
NOTE

It is not recommended to leave this option blank.

For example, if the value is 5400 seconds (90 minutes), and 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.

Ignore matching assets from the source if a subsequent asset was seen by the source before the previously fetched asset

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 may be different due to the last time the device information was updated in that adapter connection ('Last Seen' field).

  • If enabled, all connections for the adapter will ignore older device or user data (based on fetched ‘Last Seen’ field) when data for a specific device or user is received from connections of the same adapter type.
  • If disabled, all connections for the adapter will not ignore any device or user data, even if fetched from connections of the same adapter type.

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.

Enable real-time adapter (ignores all discovery cycle settings and continuously repeats fetches from the source)

This setting lets you constantly fetch adapter data. This means that once Axonius completes the discovery cycle for the adapter connection, it will initiate another cycle immediately.
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.

  • If enabled, Axonius will pull information from the adapter constantly.
  • If disabled, Axonius will not pull information from the adapter constantly.
    NOTE

    If Override the global discovery schedule for this adapter to wait X hours before fetching is configured, this setting will be ignored. The next discovery cycle for the adapter will start based on the Override the global discovery schedule for this adapter to wait X hours before fetching setting.

Was this article helpful?