Skip to main content

LogicMonitor

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

LogicMonitor is a SaaS-based monitoring platform that automates IT system monitoring. It provides a centralized view of various IT components, including networks, cloud environments, servers, and applications. LogicMonitor offers automated monitoring and data insights.

Nobl9 integrates with LogicMonitor, enabling you to create threshold and ratio SLOs for tracking the reliability of your LogicMonitor devices and websites. To do this, select the required query type—device_metrics or website_metrics—in Nobl9 and provide the necessary parameters for your LogicMonitor device or website.

LogicMonitor parameters and supported features in Nobl9
General support:
Release channel: Beta
Connection method: Agent, Direct
Replay and SLI Analyzer: Historical data limit 30 days
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:
Plugin name: n9logic_monitor
Query delay environment variable: LOGIC_MONITOR_QUERY_DELAY
Replay and SLI Analyzer: 0.81.0-beta
Query parameters retrieval: 0.76.0-beta
Timestamp cache persistence: 0.76.0-beta
Additional notes:
Create SLOs to track your LogicMonitor devices and websites
Bad over total ratio metrics

Creating SLOs with LogicMonitor​

You can create SLOs using device or website LogicMonitor metrics.

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: device_metrics
  • 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.
    Enter the Line value in uppercase.

Find out how to retrieve these values in LogicMonitor.

SLI data retrieval

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 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.

Breaking changes in Nobl9 agent 0.87.0-beta

Nobl9 agent 0.87.0-beta and later require quotation marks around these fields:

  • LogicMonitor device SLOs:

    • deviceDataSourceInstanceId
    • graphId

  • LogicMonitor website SLOs:

    • websiteId
    • checkpointId
    • graphName

Omitting quotation marks in these fields with Nobl9 agent 0.87.0-beta or later results in an error. Earlier agent versions do not require quotation marks.

Review and correct your LogicMonitor device and website SLOs as needed.

Device metrics​

Sample LogicMonitor threshold SLO
apiVersion: n9/v1alpha
kind: SLO
metadata:
  name: api-server-slo
  displayName: API Server SLO
  project: default
  labels:
    area:
      - latency
      - slow-check
    env:
      - prod
      - dev
    region:
      - us
      - eu
    team:
      - green
      - sales
  annotations:
    area: latency
    env: prod
    region: us
    team: sales
spec:
  description: Example LogicMonitor SLO
  indicator:
    metricSource:
      name: logic-monitor
      project: default
      kind: Agent
  budgetingMethod: Occurrences
  objectives:
    - displayName: Good response (200)
      value: 200
      name: ok
      target: 0.95
      rawMetric:
        query:
          logicMonitor:
            queryType: device_metrics
            deviceDataSourceInstanceId: 933147615
            graphId: 9978
            line: TIMEMAX
      op: lte
      primary: true
  service: api-server
  timeWindows:
    - unit: Month
      count: 1
      isRolling: false
      calendar:
        startTime: 2022-12-01T00:00:00.000Z
        timeZone: UTC
  alertPolicies:
    - fast-burn-5x-for-last-10m
  attachments:
    - url: https://docs.nobl9.com
      displayName: Nobl9 Documentation
  anomalyConfig:
    noData:
      alertMethods:
        - name: slack-notification
          project: default

Website metrics​

Sample LogicMonitor threshold SLO
apiVersion: n9/v1alpha
kind: SLO
metadata:
  name: api-server-slo
  displayName: API Server SLO
  project: default
  labels:
    area:
      - latency
      - slow-check
    env:
      - prod
      - dev
    region:
      - us
      - eu
    team:
      - green
      - sales
  annotations:
    area: latency
    env: prod
    region: us
    team: sales
spec:
  description: Example LogicMonitor SLO
  indicator:
    metricSource:
      name: logic-monitor
      project: default
      kind: Agent
  budgetingMethod: Occurrences
  objectives:
    - displayName: Good response (200)
      value: 200
      name: ok
      target: 0.95
      rawMetric:
        query:
          logicMonitor:
            queryType: website_metrics
            checkpointId: "7615"
            graphName: "responseTime"
            websiteId: "123213"
            line: CONNECTIONFAILURES
      op: lte
      primary: true
  service: api-server
  timeWindows:
    - unit: Month
      count: 1
      isRolling: false
      calendar:
        startTime: 2022-12-01T00:00:00.000Z
        timeZone: UTC
  alertPolicies:
    - fast-burn-5x-for-last-10m
  attachments:
    - url: https://docs.nobl9.com
      displayName: Nobl9 Documentation
  anomalyConfig:
    noData:
      alertMethods:
        - name: slack-notification
          project: default
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.

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.

Tips on retrieving SLI data in LogicMonitor​

For correct monitoring, Nobl9 SLOs based on LogicMonitor require specific data, depending on a resource you need to monitor—a device or website. To retrieve the required values, do the following:

  1. Log in to your LogicMonitor dashboard.
  2. In the navigation sidebar, click Resource Tree.
    All your monitored devices are listed here.
  3. Select the required Resource > DataSource > instance.
Device Data Source Instance ID

It's the identifier of a monitoring rule configuration or occurrence applied to a LogicMonitor device you need to monitor.

LogicMonitor UI location:
Go to the Info tab
Copy the system.instanceID property value
API endpoint for retrieval:
GET /device/devices/{deviceId}/devicedatasources/{hdsId}/instances
Nobl9 YAML definition:
deviceDataSourceInstanceId
Type: string. Put its value in quotation marks

Graph ID

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

LogicMonitor UI location:
The Graphs tab > click ellipses > Graph Definition (opens in the new tab)
The required device's URL ending
For example, XXXXX in ...exchangeDataSourceGraphs-XXXXX
API endpoint for retrieval:
GET /device/devices/{deviceId}/devicedatasources/{id}
Nobl9 YAML definition
graphId
Type: string. Put its value in quotation marks

Line

Refers to the datapoint of your required graph

LogicMonitor UI location:
The Graphs tab > click ellipses > Graph Definition (opens in the new tab)
The Datapoint value of your required graph found in the Lines table or the line.label value
API endpoint for retrieval:
GET /device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data
Nobl9 YAML definition:
line
Pass its value in uppercase

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
Last updated on
On this page