---
title: Meter node
description: Configure the Meter node to increment a custom metric key each time journey evaluation passes through the node, enabling trend monitoring with tools such as Prometheus.
component: auth-node-ref
version: 8
page_id: auth-node-ref::meter
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/meter.html
llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-meter.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/meter.html
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  properties: Properties
  outputs: Outputs
  callbacks: Callbacks
  outcomes: Outcomes
  errors: Errors
---

# Meter node

The Meter node increments a specified metric key each time evaluation passes through the node.

The custom metric defined in this node is exposed in all available interfaces, as described in [Monitor AM instances](https://docs.pingidentity.com/pingam/8/maintenance/monitoring-am.html). This lets you monitor the metric over time to observe trends using monitoring tools such as Prometheus.

## Example

The following example demonstrates using the Meter node in a multi-factor authentication (MFA) journey to track the number of times an OTP is requested via SMS:

![MFA journey with Meter node](_images/meter-node-journey.png)

* The [Page node](page.html) containing the [Platform Username node](platform-username.html) and [Platform Password node](platform-password.html) prompts for credentials.

* The [Data Store Decision node](data-store-decision.html) validates the username-password credentials.

* The [HOTP Generator node](hotp-generator.html) generates an eight-digit OTP.

* The [Choice Collector node](choice-collector.html) prompts the user to choose whether they want to receive the OTP via SMS or email.

  * If the user chooses SMS:

    * The Meter node increments the custom metric specified in the node configuration. For example, a metric called `custom.meter.otp.sms.requests`.

    * The [OTP SMS Sender node](otp-sms-sender.html) sends the OTP to the user's mobile number.

  * If the user chooses email, the [OTP Email Sender node](otp-email-sender.html) sends the OTP to the user's email address.

* The [OTP Collector Decision node](otp-collector-decision.html) prompts the user to enter the OTP they received and verifies it. If the OTP is correct, the user is authenticated.

You can then monitor the `custom.meter.otp.sms.requests` metric over time to observe how many OTP requests are made via SMS.

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

None. This node doesn't read shared state data.

## Dependencies

This node has no dependencies.

## Properties

| Property                | Usage                                                                                                               |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Metric Key *(required)* | The name of the custom metric to increment when evaluation passes through this node.Example: `custom.meter.metric`. |

## Outputs

This node doesn't change the shared state.

## Callbacks

This node doesn't send any callbacks.

## Outcomes

Single outcome path.

## Errors

This node doesn't log any error or warning messages of its own.