🐶 Datadog Custom Metrics

Helpers for sending Datadog custom metrics via hot-shots.

1yarn add seek-datadog-custom-metrics

Tagging convention

All custom metrics are prefixed by AppConfig.name. Two global tags are also added to every custom metric:

• AppConfig.environment becomes env:${value}
• AppConfig.version becomes version:${value}

These tags are consistent with tags sent by Gantry via Datadog's AWS integration.

API reference

createStatsDClient

createStatsDClient creates a hot-shots client configured with our tagging convention. This is intended for containerized services, particularly those deployed with Gantry.

1import { StatsD } from 'hot-shots';
2import { createStatsDClient } from 'seek-datadog-custom-metrics';
3
4// Expects `name`, `version`, `environment` and `metricsServer` properties
5import config from '../config';
6
7// This example assumes Bunyan/pino
8import { rootLogger } from '../logger';
9const errorHandler = (err: Error) => {
10  rootLogger.error('StatsD error', err);
11};
12
13// Returns a standard hot-shots StatsD instance
14const metricsClient = createStatsDClient(StatsD, config, errorHandler);

createLambdaExtensionClient

createLambdaExtensionClient creates a Lambda extension client. This is intended for AWS Lambda functions and is a replacement for createCloudWatchClient.

This client will only submit metrics as a distribution which enables globally accurate aggregations for percentiles (p50, p75, p90, etc).

1import { createLambdaExtensionClient } from 'seek-datadog-custom-metrics';
2
3// Expects `name` and `metrics` properties
4import config from '../config';
5
6// Returns a standard hot-shots StatsD instance
7const { metricsClient, withLambdaExtension } =
8  createLambdaExtensionClient(config);
9
10export const handler = withLambdaExtension((event, _ctx) => {
11  try {
12    logger.info('request');
13
14    await lambdaFunction(event);
15  } catch (err) {
16    logger.error({ err }, 'request');
17
18    metricsClient.increment('invocation_error');
19
20    throw new Error('invoke error');
21  }
22});

createNoOpClient

createNoOpClient returns a no-op client. This is intended for use where a MetricsClient interface is expected but you do not wish to provide one, e.g in tests.

1import { createNoOpClient } from 'seek-datadog-custom-metrics';
2
3// Returns a `MetricsClient` subset of the full StatsD interface
4const metricsClient = createNoOpClient();

createTimedSpan

createTimedSpan wraps an asynchronous closure and records custom Datadog metrics about its performance. This is intended as a lightweight alternative to APM where nested spans aren't required.

1import { createTimedSpan } from 'seek-datadog-custom-metrics';
2
3// Takes a StatsD instance or `MetricsClient`
4const timedSpan = createTimedSpan(metricsClient);
5
6const loadPrivateKey = async (): Promise<PrivateKey> =>
7  await timedSpan(
8    // Prefix for the custom metrics
9    'secrets.load_private_key',
10    // Closure to be timed
11    () => client.getSecretValue({ SecretId }).promise(),
12  );

httpTracingConfig

The dd-trace package can instrument your application and trace its outbound HTTP requests. However, its emitted trace.http.request metric only captures the HTTP method against the resource.name tag, which is not useful if your application makes HTTP requests to multiple resources and you want to inspect latency by resource.

This configuration object adds a hook to replace the resource.name with a HTTP method and semi-normalised URL. For example, if your application makes the following HTTP request:

1PUT https://www.example.com/path/to/123?idempotencyKey=c1083fb6-519c-42bf-8619-08dfd6229954

The trace.http.request metric will see the following tag change:

1- resource_name:put
2+ resource_name:put_https://www.example.com/path/to/number?idempotencyKey=uuid

Apply the configuration object where you bootstrap your application with the Datadog tracer:

1import { httpTracingConfig } from 'seek-datadog-custom-metrics';
2
3// DataDog/dd-trace-js#1118
4datadogTracer?.use('http', httpTracingConfig);

This configuration may be superseded in future if the underlying dd-trace implementation is corrected.

DataDog/dd-trace-js#1118