Introduction to New Relic Pathpoint

These are the highest level business stages. At the actual system level these will be a rollup of many services and methods and show the complete health, congestion, count and infrastructure state of a Pathpoint.

The different stages of a Pathpoint enables you to gain a high-level overview of business processes and identify the different services and methods presented at the system level for each commercial stage.

Adding stages

Adding stages is as fast as typing in the stage names.

Get real-time and historical information for each stage

View real-time details for each stage, including any errors. Stages are color-coded to indicate their status: green for normal operation, yellow for critical signals, and red for multiple anomalies requiring attention.

In addition to the current state of these indicators, Pathpoint allows for the vizualization of previous states (recently and not so recently) using "playback".

Steps are "sub-stages" of a parent stage and represent the various events occurring throughout the stage.

Steps break down stages but also offer a level of abstraction. Often steps can be represented in some sequential order, known as levels. This allows New Relic to intuitively understand if there are some sequential dependencies between steps.

Adding steps

Signals are the most granular elements in the Pathpoint model. They are often a specific application monitored by our APM or browser monitoring, but you can use any New Relic entity or alert as a signal. This provides almost limitless flexibility.

Every signal provides a snapshot of its current status, connected information, and a record of previous states.

Adding signals

Adding signals to Pathpoint is as simple as navigating a list of entities and alerts in your account. It is easy to filter them by name and add only the ones you want. No custom queries are required.

Signal status

Like the entities or alerts they are related to signals have three different health statuses, which are color-coded for easy identification:

• Green: Optimal performance. The related entity or alert is functioning as expected.
• Yellow: Warning state. The related entity or alert has an active warning condition. Some attention may be needed.
• Red: Critical state. The related entity or alert has an active critical condition. Immediate attention is needed.
• Gray: Requires attention. Potential configuration issues or data gaps exist, such as a missing alert or the telemetry is not available.

Each Pathpoint step relies on one or more signals, making signal health crucial to overall Pathpoint performance. By tracking signal status, you can effectively monitor system health and quickly identify issues.

View signal details

Signals linked to a New Relic entity adopt the entity's health status. Clicking a signal icon displays a window with detailed signal information, including:

• Open incidents
• Golden signal status
• Link to the entity's details page for deeper analysis

The image above shows the details page for an APM entity signal.

Beyond structured signals tied to New Relic entities or alerts, Pathpoint supports flexible KPI tracking via custom NRQL queries. This enables correlation of lower-level entity health with broader business impact metrics. Common use cases include monitoring event counts (such as user logins, registrations, checkouts, cart abandonment, etc.) and monetary values (such as total checkout value, returned product value, etc.). These KPIs can be derived from existing telemetry sources such as logs, custom metrics, or other data independent of specific entities.