Skip to main content

LogicMonitor

Reading time: 0 minute(s) (0 words)

LogicMonitor is a SaaS-based monitoring platform designed for automated monitoring of IT systems. It centralizes monitoring by providing a unified view of various IT components, including networks, cloud environments, servers, and applications.

It features automated monitoring and provides data insights.

LogicMonitor utilizes the LogicMonitor Collector for data collection, an installed Java application that runs on either Linux or Windows servers. Collected data is stored in a centralized data center.

Nobl9 integration with LogicMonitor allows you to create SLOs on LogicMonitor DataPoints based on a threshold (raw) or ratio (count) metrics.

LogicMonitor parameters and supported features in Nobl9
General support:
Release channel: Beta
Connection method: Agent, Direct
Replay and SLI Analyzer: Supported
Event logs: Supported
Query checker: Not supported
Query parameters retrieval: Supported
Timestamp cache persistence: Supported
Query parameters:
Query interval: 1 min
Query delay: 2 min
Jitter: 15 sec
Timeout: 30 sec
Agent details and minimum required versions for supported features:
Environment variable: LOGIC_MONITOR_QUERY_DELAY
Plugin name: n9logic_monitor
Replay and SLI Analyzer: 0.81.0-beta
Maximum historical data retrieval period: 30 days
Query parameters retrieval: 0.76.0-beta
Timestamp cache persistence: 0.76.0-beta
Additional notes:
Bad over total ratio metric

Users can add LogicMonitor as a data source and create threshold and ratio SLOs against LogicMonitor in the following ways:

Prerequisites​

Authentication to LogicMonitor requires an LMv1 token credentials—accessID and accessKey—issued for your LogicMonitor account.

For the direct connection method, you're additionally required to provide accessID and accessKey, along with your LogicMonitor account.
For the agent connection method, you need to provide your LogicMonitor account only.

You pass these credentials using the environment variables when deploying the agent.

More about creating LMv1 tokens in LogicMonitor.

More about signing API calls to LogicMonitor.

To ensure data transmission between Nobl9 and LogicMonitor, it may be necessary to list Nobl9 IP addresses as trusted.

💻ip allowlist
IP addresses to include in your allowlist for secure access:

If you're using app.nobl9.com instance:
  • 18.159.114.21
  • 18.158.132.186
  • 3.64.154.26
If you're using us1.nobl9.com instance:
  • 34.121.54.120
  • 34.123.193.191
  • 34.134.71.10
  • 35.192.105.150
  • 35.225.248.37
  • 35.226.78.175
  • 104.198.44.161

Adding LogicMonitor as a data source​

Select the preferable way to add LogicMonitor as a data source. Once added, your LogicMonitor data source becomes available on the Nobl9 Web > Integrations data source list.

Direct connection method​

Nobl9 Web​

  1. Navigate to Integrations > Sources.
  2. Click .
  3. Click the required Source button.
  4. Choose Direct.
Release channel
Currently, Nobl9 integration with LogicMonitor is available in the Beta release channel only.
  1. Enter your LogicMonitor Account.
  2. Provide your Access ID and Access Key—your LMv1 token credentials issued for your LogicMonitor account.
    Learn more about creating LMv1 tokens in LogicMonitor and signing API calls to LogicMonitor.
  1. Select a Project.
    Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
  5. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
    • The default value in LogicMonitor integration for Query delay is 2 minutes.
    info
    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
  6. Enter a Maximum Period for Historical Data Retrieval.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on this data source.
    • The maximum period value depends on the data source.
      Find the maximum value for your data source.
    • A greater period can extend the loading time when creating an SLO.
      • The value must be a positive integer.
  7. Enter a Default Period for Historical Data Retrieval.
    • It is used by SLOs connected to this data source.
    • The value must be a positive integer or 0.
    • By default, this value is set to 0. When you set it to >0, you will create SLOs with Replay.
  8. Click Add Data Source.

sloctl​

To connect the LogicMonitor data source using the direct method, apply the following configuration using the sloctl apply -f command:

apiVersion: n9/v1alpha
kind: Direct
metadata:
  # String, mandatory a-z, 0-9, and "-" only. The data source name identifier
  name: my-logic-monitor-data-source
  # String, optional. The data source user-friendly name
  displayName: My LogicMonitor data source
  # String, mandatory. The name identifier of the project to locate your data source in
  project: my-project
spec:
  # String, optional
  description: Sample LogicMonitor data source (agent connection)
  # Mandatory. Currently, beta for LogicMonitor
  releaseChannel: beta
  # Source-specific fields
  logicMonitor:
    # String, mandatory. Replace with your LogicMonitor account
    account: my-account-name
    # String, mandatory. Replace with your LogicMonitor accessID
    accessId: REDACTED
    # String, mandatory. Replace with your LogicMonitor accessKey
    accessKey: REDACTED
  # Mandatory. The query delay configuration
  queryDelay:
    value: 3
    unit: Minute
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 15
      unit: Day
FieldTypeDescription
queryDelay.unit
mandatory
enumSpecifies the unit for the query delay. Possible values: Second | Minute.
• Check query delay documentation for default unit of query delay for each source.
queryDelay.value
mandatory
numericSpecifies the value for the query delay.
• Must be a number less than 1440 minutes (24 hours).
• Check query delay documentation for default unit of query delay for each source.
releaseChannel
mandatory
enumSpecifies the release channel. Accepted values: beta | stable.
Source-specific fields
logicMonitor.account
mandatory
stringYour LogicMonitor account.
logicMonitor.accessID
mandatory
string, secretYour LogicMonitor access ID.
logicMonitor.accessKey
mandatory
string, secretYour LogicMonitor access key.

You can directly apply the YAML or save the configuration as a YAML file and pass it with the sloctl apply -f %path-to-your-file.yaml% command.

Agent connection method​

Nobl9 Web​

  1. Navigate to Integrations > Sources.
  2. Click .
  3. Click the required Source button.
  4. Choose Agent.
Release channel
Currently, Nobl9 integration with LogicMonitor is available in the Beta release channel only.
  1. Provide your LogicMonitor Account.
  1. Select a Project.
    Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
  5. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
    • The default value in LogicMonitor integration for Query delay is 2 minutes.
    info
    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
  6. Enter a Maximum Period for Historical Data Retrieval.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on this data source.
    • The maximum period value depends on the data source.
      Find the maximum value for your data source.
    • A greater period can extend the loading time when creating an SLO.
      • The value must be a positive integer.
  7. Enter a Default Period for Historical Data Retrieval.
    • It is used by SLOs connected to this data source.
    • The value must be a positive integer or 0.
    • By default, this value is set to 0. When you set it to >0, you will create SLOs with Replay.
  8. Click Add Data Source.

sloctl​

To connect the LogicMonitor data source using the agent method, apply the following configuration using the sloctl apply -f command:

apiVersion: n9/v1alpha
kind: Agent
metadata:
  # String, mandatory a-z, 0-9, and "-" only. The data source name identifier
  name: my-logic-monitor-data-source
  # String, optional. The data source user-friendly name
  displayName: My LogicMonitor data source
  # String, mandatory. The name identifier of the project to locate your data source in
  project: my-project
spec:
  # String, optional
  description: Sample LogicMonitor data source (agent connection)
  # String, mandatory. Currently, beta for LogicMonitor
  releaseChannel: beta
  # Source-specific fields
  logicMonitor:
    # String, mandatory. Replace with your LogicMonitor account
    account: my-account-name
  # Mandatory. The query delay settings
  queryDelay:
    value: 3
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 15
      unit: Day
FieldTypeDescription
queryDelay.unit
mandatory
enumSpecifies the unit for the query delay. Possible values: Second | Minute.
• Check query delay documentation for default unit of query delay for each source.
queryDelay.value
mandatory
numericSpecifies the value for the query delay.
• Must be a number less than 1440 minutes (24 hours).
• Check query delay documentation for default unit of query delay for each source.
releaseChannel
mandatory
enumSpecifies the release channel. Accepted values: beta | stable.
Source-specific fields
logicMonitor.account
mandatory
stringYour LogicMonitor account.

You can directly apply the YAML or save the configuration as a YAML file and pass it with the sloctl apply -f %path-to-your-file.yaml% command.

Agent deployment​

When you add a data source, Nobl9 automatically generates a Kubernetes configuration and a Docker command line for you to deploy the agent. Both configurations are available on the Nobl9 Web under the data source details > Agent configuration tab.

Agent deployment requires client_id and client_secret. To retrieve their values, run sloctl get agents -p <YOUR_PROJECT_NAME> -k.

If you use Kubernetes, you can apply the supplied YAML config file to a Kubernetes cluster to deploy the agent. The agent facilitates Nobl9 to import your service metrics.

DISCLAIMER: This deployment description contains only the fields necessary for the purpose of this demo. It is not a ready-to-apply k8s deployment description. Replace LOGIC_MONITOR_ACCESS_ID and LOGIC_MONITOR_ACCESS_KEY with your organization keys.

apiVersion: v1
kind: Secret
metadata:
  # String, mandatory. The deployment name identifier
  name: nobl9-agent-my-organization-my-project-logic-monitor
  namespace: my-namespace
type: Opaque
stringData:
  # Replace with your LogicMonitor access ID
  n9_logic_monitor_access_id: "<LOGIC_MONITOR_ACCESS_ID>"
  # Replace with your LogicMonitor access key
  n9_logic_monitor_access_key: "<LOGIC_MONITOR_ACCESS_KEY>"
  # Replace with your Nobl9 client ID
  client_id: "<YOUR_NOBL9_CLIENT_ID>"
  # Replace with your Nobl9 client secret
  client_secret: "<YOUR_NOBL9_CLIENT_SECRET>"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nobl9-agent-my-organization-my-project-logic-monitor
  namespace: my-namespace
spec:
  replicas: 1
  selector:
    matchLabels:
      nobl9-agent-name: "logic-monitor"
      nobl9-agent-project: "my-project"
      nobl9-agent-organization: "my-organization"
  template:
    metadata:
      labels:
        nobl9-agent-name: "logic-monitor"
        nobl9-agent-project: "my-project"
        nobl9-agent-organization: "my-organization"
    spec:
      containers:
        - name: agent-container
          image: nobl9/agent:0.88.0-beta
          resources:
            requests:
              memory: "700Mi"
              cpu: "0.2"
          env:
            - name: N9_CLIENT_ID
              valueFrom:
                secretKeyRef:
                  key: client_id
                  name: nobl9-agent-my-organization-my-project-logic-monitor
            - name: N9_LOGIC_MONITOR_ACCESS_ID
              valueFrom:
                secretKeyRef:
                  key: n9_logic_monitor_access_id
                  name: nobl9-agent-my-organization-my-project-logic-monitor
            - name: N9_LOGIC_MONITOR_ACCESS_KEY
              valueFrom:
                secretKeyRef:
                  key: n9_logic_monitor_access_key
                  name: nobl9-agent-my-organization-my-project-logic-monitor
            - name: N9_INTAKE_URL
              value: "https://{your-instance}.nobl9.com/api/input"
            - name: N9_QUERYENGINE_URL
              value: "https://{your-instance}.nobl9.com/api/queryengine"
            - name: N9_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  key: client_secret
                  name: nobl9-agent-my-organization-my-project-logic-monitor
            - name: N9_AUTH_SERVER
              value: "<YOUR_N9_AUTH_SERVER_ID>"
            - name: N9_OKTA_ORG_URL
              value: "https://accounts.nobl9.com"
            - name: N9_METRICS_PORT
              value: "9090"
            - name: N9_NATS_URL
              # A wss:// URL
              value: "<YOUR_NOBL9_NATS_URL>"

Important notes:

  • The N9_METRICS_PORT is a variable specifying the port to which the /metrics and /health endpoints are exposed.
  • 9090 is the default value and can be changed.
  • If you don’t want the metrics to be exposed, comment out or delete the N9_METRICS_PORT variable.

Creating SLOs with LogicMonitor​

Currently, you can create SLOs based on LogicMonitor and edit them using sloctl or Terraform.

Once created, your LogicMonitor SLO is available in the SLO grid. You can check its charts and other data on your SLO details page.

Tips on retrieving SLI data in LogicMonitor​

To run an SLI with Nobl9, the following values are required:

  • deviceDataSourceInstanceID
    The identifier of a monitoring rule configuration or occurrence applied to a LogicMonitor device you need to monitor.
  • graphID
    Refers to the graph configuration associated with your required device and defines how monitoring data collected by this device is visualized and presented in LogicMonitor.
  • line
    Refers to the line.label field.
  1. Log in to your LogicMonitor dashboard.
  2. In the navigation sidebar, go to Resources.
  3. Select the required instance under the data source that holds it.
  4. Under the Info tab, copy the system.instanceId value in the list of properties. Use it as the value for deviceDataSourceInstanceID.
  5. Open the Graphs tab.
  6. Unfold the graph options menu. Select Graph Definitions (opened in the new page):
  7. Find the graphID value at the end of the URL: ...exchangeDataSourceGraphs-XXXXX, where the XXXXX part is the graphID value.
  8. Go to the Lines table at the bottom of the page.
    The value under the Datapoint column is your line.
    Provide the line value in your Nobl9 SLO in upper case.

You can also retrieve these values calling the following LogicMonitor API:

  • deviceDataSourceInstanceID: GET /device/devices/{deviceId}/devicedatasources/{hdsId}/instances
  • graphID: GET /device/devices/{deviceId}/devicedatasources/{id}
  • line: GET /device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data

Pass the obtained values in the YAML file with your LogicMonitor SLO.

SLI values for good and total
When choosing the query for the ratio SLI (countMetrics), keep in mind that the values ​​resulting from that query for both good and total:
  • Must be positive.
  • While we recommend using integers, fractions are also acceptable.
    • If using fractions, we recommend them to be larger than 1e-4 = 0.0001.
  • Shouldn't be larger than 1e+20.

Nobl9 Web​

  1. Navigate to Service Level Objectives.
  2. Click .
  3. Select a Service.
    It will be the location for your SLO in Nobl9.
  4. Select your LogicMonitor data source.
  5. Modify Period for Historical Data Retrieval, when necessary.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on LogicMonitor.
    • A longer period can extend the data loading time for your SLO.
    • Must be a positive whole number up to the maximum period value you've set when adding the LogicMonitor data source.
  6. Select the Metric type:
    • Threshold metric: a single time series is evaluated against a threshold.
    • A Ratio metric: two-time series for comparison. For a ratio metric:
      • Select the Data count method: incremental or non-incremental.
      • Specify a time series for comparison against total: a good metric means a ratio of good events or bad metric, a ratio of bad events.

  1. A LogicMonitor query must follow the below patters:

    • Query Type: currently, only the device_metrics type is available
    • Device Data Source Instance ID: the identifier of a monitoring rule configuration or occurrence applied to your LogicMonitor device.
    • Graph ID: a 5-symbol graph configuration.
    • Line: the Datapoint value.
      Uppercase only.

    info

    Tips on retrieving SLI data in LogicMonitor provide instructions on retrieving the required values.

  1. Define the Time Window for your SLO:
  2. Configure the Error budget calculation method and Objectives:
    • Occurrences method counts good attempts against the count of total attempts.
    • Time Slices method measures how many good minutes were achieved (when a system operates within defined boundaries) during a time window.
    • You can define up to 12 objectives for an SLO.

      • Similar threshold values for objectives
      To use similar threshold values for different objectives in your SLO, we recommend differentiating them by setting varying decimal points for each objective.
      For example, if you want to use threshold value 1 for two objectives, set it to 1.0000001 for the first objective and to 1.0000002 for the second one.
      Learn more about threshold value uniqueness.
  3. Add the Display name, Name, and other settings for your SLO:
    • Name identifies your SLO in Nobl9. After you save the SLO, its name becomes read-only.
      Use only lowercase letters, numbers, and dashes.
    • Create Composite SLO: with this option selected, you create a composite SLO 1.0. Composite SLOs 1.0 are deprecated. They're fully operable; however, we encourage you to create new composite SLOs 2.0.
      You can create composite SLOs 2.0 with sloctl using the provided template. Alternatively, you can create a composite SLO 2.0 with Nobl9 Terraform provider.
    • Set Notifications on data. With it, Nobl9 will notify you in the cases when SLO won't be reporting data or report incomplete data for more than 15 minutes.
    • Add alert policies, labels, and links, if required.
      Up to 20 items of each type per SLO is allowed.
  4. Click CREATE SLO.

    5. SLO configuration use case
    Check the SLO configuration use case for a real-life SLO example.

sloctl​

To create an SLO based on LogicMonitor, pass the required configuration with the sloctl apply -f command. Your configuration must follow the pattern either for the threshold (raw) or ratio (count) metrics.

Refer to the YAML guide > SLO for more information about the fields.

- apiVersion: n9/v1alpha
  kind: SLO
  metadata:
    name: my-raw-slo
    displayName: My LogicMonitor threshold SLO
    project: my-project
    # Optional
    labels:
      key-1:
        - value-1
        - value-2
      key-2:
        - value-1
        - value-2
    # Optional
    annotations:
      key-1: value-1
      key-2: value-2
  spec:
    description: Sample LogicMonitor threshold SLO
    indicator:
      metricSource:
        name: my-logic-monitor-data-source
        project: my-project
        kind: Direct
    budgetingMethod: Occurrences
    objectives:
      - displayName: Good response (200)
        value: 200.0
        name: good-response
        target: 0.95
        rawMetric:
          query:
            logicMonitor:
              queryType: device_metrics
              # Numeric, mandatory.
              # The identifier of a monitoring rule configuration or occurrence applied to a LogicMonitor device you need to monitor
              deviceDataSourceInstanceId: <YOUR_SYSTEM_INSTANCE_ID>
              # Numeric, mandatory.
              # A 5-digit identifier of the configuration of the graph associated with the device you need to monitor
              graphId: <YOUR_GRAPH_ID>
              # String, mandatory. Uppercase only. The Lines > Datapoint value
              line: <YOUR_LINE_VALUE>
        op: lte
        primary: true
    service: my-service
    timeWindows:
      - unit: Month
        count: 1
        isRolling: false
        calendar:
          startTime: 2022-12-01 00:00:00
          timeZone: UTC
    # Optional
    alertPolicies:
      - my-alert-policy-1
      - my-alert-policy-2
    # Optional
    attachments:
      - url: https://{my-website}.com
        displayName: My website attached to this SLO
    # Optional. The No-data anomaly notifications (beta)
    anomalyConfig:
      noData:
        alertMethods:
          - name: my-alert-method
            project: my-project

Find more SLO samples in the Nobl9 SDK.

To check your created SLO with sloctl, run sloctl get slos. Also, you can check it on the Nobl9 Web in the SLO grid page.

You can replay your LogicMonitor SLOs in the following ways:

  • Go to the required SLO details. Click More Actions > Run Replay.
  • Run sloctl replay.

LogicMonitor API rate limits​

LogicMonitor limits GET requests to 500 per minute.

Read more about rate limiting in LogicMonitor.

You can optimize the rate limit usage, which is particularly beneficial when you have hundreds of SLIs. For this, keep an individual data source in Nobl9 per LogicMonitor instance, ensuring a single rate limit.

It makes possible batching queries by graphId and instanceId and reading time series from responses per graphId, instanceId, and line (an SLI identifier). As a result, Nobl9 can query for unique lines only once, even if graphId and instanceId include multiple lines.

The maximum number of lines graphId and instanceId can return varies by case and depends on how metrics are organized.

For a more in-depth look, consult additional resources:
Creating LMv1 tokens in LogicMonitorLogicMonitor documentationSigning API calls to LogicMonitorLogicMonitor documentationRate limiting in LogicMonitorLogicMonitor documentationNobl9 agent requirementsNobl9 agentsloctl user guidesloctlConfiguring sloctl contextsloctlsloctl common objectssloctlsloctl applysloctlCreating an agent connection using the Nobl9 Terraform providerTerraformCreating a direct connection using the Nobl9 Terraform providerTerraformCreating SLOs using the Nobl9 Terraform providerTerraform
On this page