LogicMonitor
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: 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
Users can add LogicMonitor as a data source and create threshold and ratio SLOs against LogicMonitor in the following ways:
- Nobl9 Web wizardsβthe direct and agent connection methods, and SLOs
sloctl
βthe direct and agent connection methods, and SLOs- The Nobl9 Terraform Providerβthe direct and agent connection methods, and SLOs
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.
app.nobl9.com
instance:- 18.159.114.21
- 18.158.132.186
- 3.64.154.26
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β
- Navigate to Integrations > Sources.
- Click
.
- Click the required Source button.
- Choose Direct.
- Enter your LogicMonitor Account.
- 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.
- 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 thedefault
project. - Enter a Display Name.
You can enter a user-friendly name with spaces in this field. - 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. - Enter a Description.
Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it. - 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
.
infoChanging the Query delay may affect your SLI data. For more details, check the Query delay documentation. - The default value in LogicMonitor integration for Query delay is
- 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.
- 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.
- Click Add Data Source
sloctlβ
- Create a YAML definition to set up a direct connection with LogicMonitor. For this, refer to the following example:
apiVersion: n9/v1alpha
kind: Direct
metadata:
name: logic-monitor
displayName: LogicMonitor Direct
project: default
spec:
description: Example LogicMonitor Direct
releaseChannel: beta
logicMonitor:
account: my-account-name
accessId: 9xA2BssShK21ld9LoOYu
accessKey: "[secret]"
historicalDataRetrieval:
maxDuration:
value: 30
unit: Day
defaultDuration:
value: 15
unit: Day
queryDelay:
value: 3
unit: Minute
Field | Type | Description |
---|---|---|
queryDelay.unit mandatory | enum | Specifies 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 | numeric | Specifies 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 | enum | Specifies the release channel. Accepted values: beta | stable . |
Source-specific fields | ||
logicMonitor.account mandatory | string | Your LogicMonitor account. |
logicMonitor.accessID mandatory | string, secret | Your LogicMonitor access ID. |
logicMonitor.accessKey mandatory | string, secret | Your LogicMonitor access key. |
- Apply your YAML definition using the
sloctl apply
command.
Agent connection methodβ
Nobl9 Webβ
- Navigate to Integrations > Sources.
- Click
.
- Click the required Source button.
- Choose Agent.
- Provide your LogicMonitor Account.
- 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 thedefault
project. - Enter a Display Name.
You can enter a user-friendly name with spaces in this field. - 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. - Enter a Description.
Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it. - 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
.
infoChanging the Query delay may affect your SLI data. For more details, check the Query delay documentation. - The default value in LogicMonitor integration for Query delay is
- 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.
- 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.
- Click Add Data Source
- Deploy your agent in a Kubernetes cluster or Docker container.
sloctlβ
- Create a YAML definition to set up an agent connection with LogicMonitor. For this, refer to the following example:
apiVersion: n9/v1alpha
kind: Agent
metadata:
name: logic-monitor
displayName: LogicMonitor Agent
project: default
spec:
description: Example LogicMonitor Agent
releaseChannel: beta
logicMonitor:
account: my-account-name
historicalDataRetrieval:
maxDuration:
value: 30
unit: Day
defaultDuration:
value: 15
unit: Day
queryDelay:
value: 3
unit: Minute
Field | Type | Description |
---|---|---|
queryDelay.unit mandatory | enum | Specifies 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 | numeric | Specifies 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 | enum | Specifies the release channel. Accepted values: beta | stable . |
Source-specific fields | ||
logicMonitor.account mandatory | string | Your LogicMonitor account. |
- Apply your YAML definition using the
sloctl apply
command. - Deploy your agent in a Kubernetes cluster or Docker container.
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.