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.

Types of stages

The stages are defined as either a Person or a Process stage.

In the image above, you can see the symbols for the two types of stages:

• The one to count processes
• The one to count people

Each Pathpoint stage is defined to either count people or processes, by the touchpoints under the steps it has. If a step, under a stage, has touchpoints of the PCC (process count), then the stage will show the process count symbol. Likewise, if a step, under a stage, has touchpoints of the PRC (people count) under it, then the stage will show the people count symbol.

Get real-time information for each stage

You can view real-time information related to a particular stage including any errors associated with it. You can see if any of the associated touchpoints for a particular stage are critical, in which case the stage will turn yellow. If everything is working normally, the stage will stay green. If all touchpoints have anomalies that need to be resolved, the stage will turn red.

In addition to these indicators, Pathpoint also provides color-coded representation for congestion on the stage. If the stage turns blue, it indicates congestion, as shown in the example above. If the stage is free of congestion, the color of the stage will be white. These visual cues help you quickly identify issues and take action to resolve them.

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

You can set up steps in the traditional sequential manner (1, 2, 3...) but also in parallel to represent optional and simultaneous actions and activities.

Touchpoints are the most granular entities of the Pathpoint model. They are often a specific application monitored by our APM or browser monitoring, but you can use any NRQL query as a touchpoint as well.

Each touchpoint holds its own health, status, performance metrics, count, and business knowledge related to a specific data object, environment, application, device, API, or service and they can also be customized to fit a specific journey's goal.

Touchpoint status

Touchpoints have three different health statuses, which are color-coded for easy identification:

• Green: The touchpoint is healthy, and everything is working as expected.
• Gray: The touchpoint requires attention, and there might be some issues that need to be addressed.
• Red: The touchpoint is in a fail state, and there are critical issues that require immediate attention.

Every step in Pathpoint is connected to one or more touchpoints. As such, the health status of every step is dependent on the status of its respective touchpoints. Therefore, touchpoints are considered the pulse of each Pathpoint. By monitoring the status of touchpoints, you can gain insights into the health of the entire system and identify any anomalies that need attention.

View touchpoint query

Queries allow you to determine all the parameters that you should consider for a particular touchpoint. They are pre-programmed on a file called JSON configuration file, that you can also manually tweak to fit a specific journey's goal.

To view or edit the query of a touchpoint:

1. Right click on the touchpoint you want to work with.
2. Click Queries.
3. Edit the query and click Save / Update.

The image above shows the query associated with Login people (PRC) touchpoint.