Documentation Plugins LogicMonitor Devices

LogicMonitor Devices data source

The LogicMonitor Devices data source allows you to query and visualize LogicMonitor device metrics in Grafana.

Supported features

Before you begin

Before configuring the LogicMonitor Devices data source, ensure you have:

• Grafana permissions: Organization administrator role to add data sources
• LogicMonitor account: Access to a LogicMonitor portal with REST API v3 bearer token
• Grafana version: Grafana 11.6.7 or later, on any free or paid Grafana Cloud plan or on a self-managed instance with an activated Grafana Enterprise license

Install the plugin

To install the data source, refer to the Installation guide.

Configure the data source

To add the LogicMonitor Devices data source:

1. Click Connections in the left-side menu.
2. Click Add new connection.
3. Type LogicMonitor in the search bar.
4. Select LogicMonitor Devices.
5. Click Add new data source.

After the data source form opens, complete the fields in the following sections.

Basic settings

Authentication

This plugin supports bearer token-based authentication. To create a token:

1. Log in to your LogicMonitor portal.
2. Navigate to Settings > Users and Roles.
3. (Optional) Add a new user with a readonly role if one doesn’t already exist.
4. Go to the Bearer Tokens tab.
5. Create a new token for the associated user.

Verify the connection

Click Save & test to verify the connection. A successful test displays the message “health check succeeded for ‘metrics usage details’ query”. If the connection fails, refer to Troubleshoot LogicMonitor data source issues.

Provision the data source

You can configure this data source using configuration files with the Grafana provisioning system. For more information, refer to Provisioning Grafana data sources.

Example provisioning configuration:

YAML Copy

apiVersion: 1
datasources:
  - name: LogicMonitor
    type: grafana-logicmonitor-datasource
    jsonData:
      variables:
        account_name: <ACCOUNT_NAME>
      authMethod: bearer
    secureJsonData:
      logicmonitor.token: <TOKEN>

Replace <ACCOUNT_NAME> with your LogicMonitor account name and <TOKEN> with your LogicMonitor REST API v3 bearer token.

Provision the data source with Terraform

You can configure this data source using the Grafana Terraform provider.

hcl Copy

resource "grafana_data_source" "logicmonitor" {
  type = "grafana-logicmonitor-datasource"
  name = "LogicMonitor"

  json_data_encoded = jsonencode({
    variables = {
      account_name = "<ACCOUNT_NAME>"
    }
    authMethod = "bearer"
  })

  secure_json_data_encoded = jsonencode({
    "logicmonitor.token" = "<TOKEN>"
  })
}

Replace <ACCOUNT_NAME> with your LogicMonitor account name and <TOKEN> with your LogicMonitor REST API v3 bearer token.

Query the data source

The query editor allows you to run queries by selecting an Action Type and providing the required parameters.

The Device drop-down filters server-side as you type. The plugin sends the typed value to LogicMonitor as a displayName~"<value>" glob filter, so matching happens against the full inventory rather than only the results already loaded in the browser.

The Datasource drop-down filters client-side against the data sources already loaded for the selected device, so filtering only starts narrowing results after you pick a Device.

Keep two points in mind when using the server-side filter on the Device drop-down:

• Filtering matches the LogicMonitor displayName field. Devices with the same display name appear together in the results.
• Special characters such as " and \ must be escaped in LogicMonitor glob filters. If typed values contain these characters, the filter returns no matches. Avoid those characters or scope the query with a template variable instead.

Device Instance Data

Retrieve time series data for individual device instances.

Device Instance Data By Device Group

Retrieve time series data for devices within a specific device group.

Table queries

Use these query types to retrieve and display data in table format:

• Devices: Lists all available devices in your LogicMonitor account.
• Datasources: Lists all data sources within a selected device.
• Instances: Lists all instances within a selected device and data source.

Large result sets and pagination

The data source paginates every list query against the LogicMonitor REST API using offset-based paging. Each request asks for 1000 results, and the plugin follows successive pages until the API reports no more items or an internal safety cap is reached.

• Default page size: 1000 items per request.
• Default safety cap: 10 pages per query, so a single selector or table query fetches up to approximately 10,000 items before stopping.
• Selector “load more” path: The Device, Device Group, Datasource, and Instance drop-downs use an on-demand pagination path in the query editor. Each additional page loads only when you request it, so this path isn’t bounded by the same cap as the eager fetch.
• Rate-limit impact: Because a single list query can issue up to maxPages API requests, pagination increases the number of requests per query. Refer to Default rate limits when tuning dashboard refresh intervals.

Accounts larger than the effective cap still see truncated lists. To narrow results:

• Use the server-side type-to-filter behavior on the Device drop-down to narrow results before picking downstream selectors.
• Scope dashboards with template variables instead of listing every device or group.
• Split large dashboards into smaller ones by device group to keep each query within the effective cap.

Query examples

The following examples show common use cases for querying LogicMonitor data.

Monitor CPU utilization

To monitor CPU performance for a specific device:

1. Select Device Instance Data as the action type.
2. Select your target device from the Device drop-down.
3. Select CPU from the Datasource drop-down.
4. Select the CPU instance from the Instance drop-down.
5. (Optional) Select specific data points such as cpu_utilization from DataPoints.

Compare devices across a group

To compare metrics across all devices in a group:

1. Select Device Instance Data By Device Group as the action type.
2. Select your device group from the Device Group drop-down.
3. Select a device, data source, and instance.
4. Duplicate the query for each device you want to compare.

Use Explore

Use Explore to run queries and visualize results without building a dashboard. For more information, refer to Explore.

Template variables

Use template variables to create dynamic, reusable dashboards.

To add a LogicMonitor query variable:

1. Navigate to Dashboard settings > Variables.
2. Click Add variable.
3. Select Query as the variable type.
4. Select the LogicMonitor Devices data source.
5. Enter your query.

For more information about adding query variables, refer to Add a query variable.

After creating a variable, use it in your LogicMonitor queries with variable syntax. For more information, refer to Templates and variables.

Set up alerting

The LogicMonitor Devices data source supports Grafana alerting on Device Instance Data metrics.

To create an alert rule:

1. Create a panel with a LogicMonitor Device Instance Data query.
2. Click Alert in the panel edit view.
3. Click Create alert rule from this panel.
4. Configure the alert conditions based on your LogicMonitor metrics.
5. Set notification policies and contact points.

For more information about Grafana alerting, refer to Grafana Alerting.

Add annotations

Annotations allow you to mark points on a graph with rich events. You can use LogicMonitor data to create annotations on your dashboards.

To add an annotation query:

1. Navigate to Dashboard settings > Annotations.
2. Click Add annotation query.
3. Select the LogicMonitor Devices data source.
4. Configure a query that returns the events you want to annotate.

For more information about annotations, refer to Annotate visualizations.

API rate limits and performance

The LogicMonitor REST API enforces rate limits on every request. Limits apply per endpoint and HTTP method, and are shared across your entire LogicMonitor account, not per user or per bearer token. Understanding these limits helps you design dashboards that perform well and avoid query errors during heavy use.

When a request exceeds a rate limit, LogicMonitor returns an HTTP 429 response and the data source surfaces the error in the affected panel.

Default rate limits

The data source issues only GET requests. The default limit and the per-endpoint exceptions that apply to this plugin are:

For the complete list of LogicMonitor API rate limits and response headers (X-Rate-Limit-Limit, X-Rate-Limit-Remaining, X-Rate-Limit-Window), refer to REST API Rate Limit in the LogicMonitor documentation.

Reduce API usage

A single Device Instance Data panel can issue several API requests as you build the query (one each for devices, data sources, instances, and time series data). When the dashboard refreshes, only the time series request runs per panel. To stay within rate limits:

• Increase dashboard refresh intervals. Short intervals (for example, 5s or 10s) on dashboards with many panels can quickly approach account-wide limits.
• Limit the number of panels per dashboard. Each panel issues at least one request per refresh.
• Use template variables to scope dashboards instead of duplicating panels for each device.
• Stagger heavy dashboards. Avoid loading multiple LogicMonitor dashboards simultaneously across many users.

Troubleshoot LogicMonitor data source issues

This section provides solutions to common issues when configuring or using the LogicMonitor Devices data source. Entries are grouped by the layer where the problem surfaces, from the network up through alerting.

Connection errors

Connection errors indicate that Grafana can’t reach <account>.logicmonitor.com at all, so the request never reaches LogicMonitor authentication.

Authentication errors

Authentication errors indicate that Grafana reached the LogicMonitor API but the request was rejected before it could return data.

Query errors

Query errors surface when the API request succeeds but the data source can’t build a complete result.

Rate-limit errors

The plugin issues one API request per selector page and one per time series panel refresh. Pagination can multiply the request count per query up to the effective page cap.

Symptoms

• Panels show status code: 429 or Too Many Requests.
• Dashboards intermittently fail to load some panels while others succeed.

Cause

The LogicMonitor REST API rate limit for the affected endpoint has been reached across the entire account. Limits are per endpoint and shared across all bearer tokens.

Solutions

1. Increase dashboard refresh intervals so fewer requests hit each endpoint per minute.
2. Reduce the number of LogicMonitor panels on a single dashboard, or stagger loads across dashboards.
3. Use template variables to reduce the number of duplicate queries.
4. Review the specific endpoint’s default limit in Default rate limits and contact your LogicMonitor customer success manager if your usage consistently exceeds the limit.

Alert rule errors

Alert rules evaluate queries outside a dashboard panel context, so time and variable substitutions behave differently from the panel preview.

Template variable errors

Template variable queries evaluate before any panel query, so referenced parameters must resolve at variable-eval time.

Debug logging

To capture additional diagnostic information for a support case, enable debug logging in Grafana.

1. Open your Grafana configuration file (typically grafana.ini on self-managed installations) and set [log] level = debug. On Grafana Cloud, contact support to enable debug logging temporarily.
2. Alternatively, set the environment variable GF_LOG_LEVEL=debug on the Grafana process.
3. Restart Grafana for the setting to take effect.

The LogicMonitor data source writes its debug output to the standard Grafana server log. No plugin-specific environment variables are required.

Get additional help

If you’ve tried the solutions in this document and still encounter issues:

• Check the Grafana community forums for similar issues.
• Consult the LogicMonitor API documentation for service-specific guidance.
• Contact Grafana Support if you’re a Grafana Enterprise, Cloud Pro, or Cloud Contracted user.

When reporting issues, include:

• Grafana version
• LogicMonitor plugin version
• Error messages (redact sensitive information)
• Steps to reproduce
• Data source configuration (redact credentials)

Plugin updates

Always ensure that your plugin version is up-to-date so you have access to all current features and improvements. Navigate to Plugins and data > Plugins to check for updates. Grafana recommends upgrading to the latest Grafana version, and this applies to plugins as well.

Learn more

• Grafana Alerting
• Annotate visualizations
• Templates and variables
• Transformations
• LogicMonitor REST API documentation