Skip to main content

LogicMonitor

Visualize LogicMonitor devices in the JupiterOne graph. Use this integration as part of a Unified Device use case.

Installation​

The LogicMonitor integration authenticates with an API token created for a user in your LogicMonitor account. You can use either an LMv1 token (an Access ID and Access Key pair) or a Bearer Token. Choose whichever token type suits your environment when you configure the instance.

Requirements​

  • A LogicMonitor user who can create API tokens. Any user role except the out-of-the-box administrator role can create tokens, and the Allow Creation of API Token checkbox must be enabled under Settings > User Profile.
  • The user the token belongs to must have View permission on the resource groups you want to ingest. Devices are only returned for groups the token's user can view.
  • You must have permission in JupiterOne to install new integrations.
note

LogicMonitor assigns permissions at the resource-group level, and the API acts as the token's user. A device is ingested only if the token's user holds View permission on the group that contains it.

Configuration in LogicMonitor​

Creating an instance requires one of the following token types.

Create an LMv1 token (Access ID and Access Key)​

  1. In LogicMonitor, navigate to Settings > User Access > Users and Roles > LMv1 API Token.
  2. Select the Add API Token (+) icon.
  3. In the User field, select the user the token should act as. The Access ID and Access Key are populated automatically.
  4. Select Save.
  5. Copy and store the Access Key in a secure location, following your organization's security policies. It is shown only once.

Create a Bearer Token​

  1. Follow the instructions in LogicMonitor's Adding a Bearer Token guide to create a Bearer Token.
  2. Save the token in a secure location, following your organization's security policies.

Configuration in JupiterOne​

  1. From the top navigation of the JupiterOne Search homepage, select Integrations.
  2. Search for LogicMonitor and select it.
  3. Select Add Instance and configure the following settings:
  • Enter the Account Name by which you'd like to identify this LogicMonitor instance in JupiterOne. Ingested entities have this value stored in tag.AccountName when Tag with Account Name is checked.
  • Enter a Description that will further assist your team when identifying the integration instance.
  • Select a Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.
  • Enter the Company Subdomain. You can find it in the URL when you log into LogicMonitor. For example, if you log in at https://<your-company>.logicmonitor.com, then <your-company> is the company subdomain.
  • Select the token type you created and provide its credentials:
    • For Bearer Token, enter the Bearer Token generated for use by JupiterOne.
    • For LMv1 Auth, enter the Access ID and Access Key of the user account whose token you created.
  1. Select Create Configuration once all values are provided.

Advanced Configuration​

FieldDescriptionDefault
Custom Device PropertiesA comma-separated list of properties to include on each ingested device entity, for example sys.id,cust.field.data.None

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.