LogicMonitor.Api
3.240.67
See the version list below for details.
dotnet add package LogicMonitor.Api --version 3.240.67
NuGet\Install-Package LogicMonitor.Api -Version 3.240.67
<PackageReference Include="LogicMonitor.Api" Version="3.240.67" />
<PackageVersion Include="LogicMonitor.Api" Version="3.240.67" />
<PackageReference Include="LogicMonitor.Api" />
paket add LogicMonitor.Api --version 3.240.67
#r "nuget: LogicMonitor.Api, 3.240.67"
#:package LogicMonitor.Api@3.240.67
#addin nuget:?package=LogicMonitor.Api&version=3.240.67
#tool nuget:?package=LogicMonitor.Api&version=3.240.67
LogicMonitor.Api
The LogicMonitor REST API nuget package, authored by Panoramic Data Limited.
If you want some LogicMonitor software developed, come find us at: https://www.panoramicdata.com/ !
To get started, watch the videos here:
http://www.panoramicdata.com/products/logicmonitor-api-nuget-package/
A simple example:
using LogicMonitor.Api;
[...]
public static async Task GetAllResources(ILogger logger, CancellationToken cancellationToken)
{
using var logicMonitorClient = new LogicMonitorClient(
new LogicMonitorClientOptions
{
Account = "acme",
AccessId = "accessId",
AccessKey = "accessKey",
Logger = logger
}
);
var resources = await logicMonitorClient
.GetAllAsync<Resource>(cancellationToken)
.ConfigureAwait(false);
Console.WriteLine($"Resource Count: {resources.Count}");
}
LogicModule Export/Import (JSON Format)
The modern LogicMonitor UI exports LogicModules to JSON format. This library supports both JSON and XML export/import:
// Export a DataSource as JSON (modern UI format)
var json = await logicMonitorClient
.GetDataSourceJsonAsync(dataSourceId, cancellationToken);
// Export a DataSource as XML (legacy format)
var xml = await logicMonitorClient
.GetDataSourceXmlAsync(dataSourceId, cancellationToken);
// Generic export by LogicModuleType
var json = await logicMonitorClient
.GetLogicModuleJsonAsync(LogicModuleType.DataSource, dataSourceId, cancellationToken);
// Export to a file
await logicMonitorClient
.ExportLogicModuleToJsonFileAsync(
LogicModuleType.DataSource,
dataSourceId,
"datasource.json",
cancellationToken);
// Import from JSON string
var imported = await logicMonitorClient
.ImportDataSourceJsonAsync(json, cancellationToken);
// Import from file
var imported = await logicMonitorClient
.ImportDataSourceFromJsonFileAsync("datasource.json", cancellationToken);
Supported LogicModule types for export/import:
- DataSource
- EventSource
- ConfigSource
- PropertySource
- TopologySource
- JobMonitor
- AppliesToFunction
NEW! Uptime Resources (LM Uptime ping & web checks)
LM Uptime is LogicMonitor's replacement for the legacy Websites product. This library provides a strongly-typed surface for creating and managing internal/external ping and web checks as first-class resources. See docs/UptimeResources.md for a detailed guide, including how it is backed by Resources and custom properties.
using LogicMonitor.Api.Resources.Uptime;
var pingCheck = await logicMonitorClient.CreateAsync(
new PingCheckResourceCreationDto
{
Name = "dns-google-ping",
HostName = "8.8.8.8",
PreferredCollectorId = collectorId,
SyntheticsCollectorIds = [collectorId],
TestLocation = new UptimeTestLocation { CollectorIds = [collectorId] }
},
cancellationToken);
var fetched = await logicMonitorClient.GetAsync<PingCheckResource>(pingCheck.Id, cancellationToken);
API Documentation
For more information on the LogicMonitor REST API, see the official documentation.
License
This project is licensed under the MIT License - see the LICENSE file for details.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.11)
- Newtonsoft.Json (>= 13.0.4)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on LogicMonitor.Api:
| Package | Downloads |
|---|---|
|
LogicMonitor.Datamart
LogicMonitor Datamart |
|
|
LogicMonitor.Cli
Creates a template LogicMonitor project for .NET. To install (or update) the template, type: dotnet new install LogicMonitor.Cli If you do not specify the namespace with --name, the folder name is used instead Once installed, go to an empty folder and type: dotnet new logicmonitor [--name Project.Namespace] Then modify the appsettings.json file to include your LogicMonitor account, Access Id and Access Key. After this, build and run with: dotnet run This should provide some basic information about your LogicMonitor account to demonstrate a working project. |
|
|
Serilog.Sinks.LogicMonitor
Serilog sink for LogicMonitor's LM Logs |
|
|
LogicMonitor.PowerShell
A PowerShell module wrapper for the LogicMonitor.Api .NET library |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 3.240.82 | 81 | 9/7/2026 |
| 3.240.79 | 73 | 9/7/2026 |
| 3.240.71 | 64 | 9/5/2026 |
| 3.240.67 | 62 | 9/4/2026 |
| 3.240.64 | 60 | 9/4/2026 |
| 3.240.61 | 56 | 9/4/2026 |
| 3.240.56 | 110 | 8/30/2026 |
| 3.240.46 | 312 | 8/28/2026 |
| 3.240.39 | 152 | 8/19/2026 |
| 3.240.34 | 173 | 8/11/2026 |
| 3.240.33 | 144 | 7/25/2026 |
| 3.240.32 | 122 | 7/25/2026 |
| 3.240.31 | 279 | 7/23/2026 |
| 3.240.30 | 172 | 7/23/2026 |
| 3.240.29 | 124 | 7/23/2026 |
| 3.240.27 | 224 | 7/23/2026 |
| 3.240.24 | 141 | 7/22/2026 |
| 3.240.20 | 173 | 7/6/2026 |
| 3.240.19 | 137 | 7/5/2026 |
| 3.240.14 | 163 | 7/3/2026 |
v3.240.67:
- Changed: rate-limit backoff is now logged at Information, and at Warning once the cumulative
wait for a request exceeds a full MaximumBackOffSeconds. Four of the five backoff sites logged
at Debug, so a client running at the default Information level saw nothing at all while the
429 loop waited - and that wait is unbounded in aggregate and silent by every other measure:
no CPU, no open socket, no exception. Telling a polite backoff from a hung call previously
meant thread dumps and socket sampling. The message now also carries the attempt number and
the total waited so far, not just the current delay, because the tenth five-minute wait reads
very differently from the first and only the client knows which it is.
- Unchanged, deliberately: the 429 retry loop is still unbounded. Waiting as long as the portal
asks is defensible, and bounding it is a policy decision for callers rather than for this
client. The six Service Unavailable retry sites also remain at Debug, since those are bounded
by AttemptCount and so cannot wait indefinitely.