PanoramicData.Datadog.Api 2.1.41

dotnet add package PanoramicData.Datadog.Api --version 2.1.41
                    
NuGet\Install-Package PanoramicData.Datadog.Api -Version 2.1.41
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="PanoramicData.Datadog.Api" Version="2.1.41" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PanoramicData.Datadog.Api" Version="2.1.41" />
                    
Directory.Packages.props
<PackageReference Include="PanoramicData.Datadog.Api" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add PanoramicData.Datadog.Api --version 2.1.41
                    
#r "nuget: PanoramicData.Datadog.Api, 2.1.41"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package PanoramicData.Datadog.Api@2.1.41
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=PanoramicData.Datadog.Api&version=2.1.41
                    
Install as a Cake Addin
#tool nuget:?package=PanoramicData.Datadog.Api&version=2.1.41
                    
Install as a Cake Tool

License: MIT

NuGet version

Codacy Badge

PanoramicData.Datadog.Api

Need help with APIs or .NET? Panoramic Data are experts in APIs and .NET, and we can help with your development. Contact us or see our software services.

A .NET API for Datadog

Supports .NET 11.0.

Installation

dotnet add package PanoramicData.Datadog.Api

Unit Tests

To run unit tests, set up your unit test User secrets to match the usersecrets.example.json file.

Usage

using Datadog.Api;

var client = new DatadogClient(new()
{
	ApiKey = "API_KEY",
	ApplicationKey = "APPLICATION_KEY"
});

var users = await client.Users.GetAllAsync();

Filtered requests

Endpoints that accept query filters take a request object:

var metrics = await client.Metrics.GetMetricsAsync(
    new GetMetricsRequest
    {
        FilterConfigured = true,
        FilterMetricType = MetricType.Gauge,
        WindowSeconds = 3600
    },
    cancellationToken);

The older overloads that took each filter as an optional parameter are obsolete and will be removed in 3.0. They produce identical requests, so migration is mechanical.

Product Compatible and additional computed target framework versions.
.NET net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.1.41 57 11/17/2026
2.1.40 69 11/15/2026
2.1.5 127 9/12/2026
2.1.2 118 9/8/2026
2.0.25 119 9/3/2026
2.0.9 363 12/18/2025
2.0.7 219 1/7/2025
2.0.5 251 6/11/2024

Security fix: sensitive HTTP headers are now redacted in diagnostic output.

     Previously AuthenticatedHttpClientHandler joined every request and response header, key and
     value, into its Debug level log message. The handler adds DD-API-KEY and DD-APPLICATION-KEY to
     each request, so both keys were written verbatim. Any consumer running at Debug retained usable
     credentials for the life of its log store, and neither key expires.

     DD-API-KEY and DD-APPLICATION-KEY are now redacted, along with Authorization,
     Proxy-Authorization, Cookie, Set-Cookie and common API key header names, case-insensitively, on
     request and response. The credential length is retained, so requests remain diagnosable without
     exposing the value. The log line format is otherwise unchanged.

     Consumers should upgrade, review existing Debug logs for previously captured keys, and rotate
     any key that appears in them.

     Filtered endpoints on IMetrics, ITeams and IUsage now take a request object. The old
     optional-parameter overloads still work but are obsolete and will be removed in 3.0; they
     produce byte-identical requests, so migration is mechanical.

     Breaking: GetMetadataAsync and GetRelatedAssetsAsync now require a CancellationToken, matching
     the rest of the library.