Axonius Documentation
Start typing to search…

LogicMonitor

LogicMonitor is an automated infrastructure monitoring platform for enterprise IT and managed service providers.

Asset Types Fetched

  • Devices

Before You Begin

Ports

  • TCP port 443

Authentication Method

  • Access ID/Key

APIs

Axonius uses the LogicMonitor REST API V1.

Permissions

The values supplied in Access ID and Access Key API token parameters require a user with read access to devices.

To generate an API token:

  1. Login as an administrator
  2. Create a user and to assign that user privileges to use the API and which endpoints that user can access. The user must have 'Read Only access to Device permissions.
  3. Generates an Access ID and an Access Key, which are used to perform the API authentication.

For more details on generating API token in LogicMonitor, see API Tokens.

Connecting the Adapter in Axonius

To connect the adapter in Axonius, provide the following parameters:

Required Parameters

  1. Hostname or IP Address - The hostname or IP address of the LogicMonitor server.
  2. Access ID and Access Key - The API token for a user account that has the Required Permissions to fetch assets.
logicmonitor

Optional Parameters

  1. Custom property keys to convert to Axonius fields (comma separated list) - Enter a list of LogicMonitor custom property keys to convert to fields in Axonius.

  2. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  3. HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Advanced Settings

📘

Note

Advanced settings can either apply to all connections for this adapter, or to a specific connection. Refer to ​Advanced Configuration for Adapters.

  1. Parse system hostname value into hostname field - Select this option to fill the hostname field with the value of a field called system.hostname.

  2. Auto properties to parse dynamically - Enter fields from the autoProperties field in the device's JSON to dynamically parse them into queryable fields (both common and specific). Each string should adhere to the following format: title_of_the_field_in_axonius | name_of_the_field_in_autoProperties.

📘

Example

Device Manufacturer Serial | auto.bios.serial_number

If the title the customer gave does not exist, a new field is created in Axonius to accommodate that. The fields are parsed in the order they are listed in the configuration. In cases where the same field is inserted multiple times with different raw values, the value from the first occurrence in the configuration takes precedence.

For example, if both of the following values are in the configuration

  • Asset Name | auto.cmdb.name

  • Asset Name | auto.cmdb.hostname

    the system first checks if auto.cmdb.name has a value. If it does, that value is used. Otherwise, it checks auto.cmdb.hostname as a fallback.

  1. Parse OS information from system.collectorplatform - Select this option to parse OS information from system.collectorplatform if "hp" appears in system.sysinfo.
  2. Fetch instances - Select this option to fetch device instances.
  3. Parse Hostname from Azure - Select this option to parse the value for 'Host Name' from the field systemProperties -> system.azure.resourcename. If Parse system hostname value into hostname field is also enabled, this will prioritize the value from Azure over the value from the ‘hostname’ field. However, if the value in the Azure field is empty, the value from ‘hostname’ will be taken.
📘

Note

To learn more about Adapter Configuration tab advanced settings, see Adapter Advanced Settings.

Updated 4 days ago