Some New Relic features, like distributed tracing and Incident Intelligence, display topological maps that show relationships between your New Relic-monitored entities and other external hosts and services. These maps can help you diagnose and correct issues.
Map display
The exact display of these maps depends on the New Relic feature in which they're located, but there are some common visual elements. The typical map view uses hexagon icons to represent your monitored entities and other external hosts or services. The relationships between entities are represented as lines, with arrows indicating call direction.
This is an Incident Intelligence issues map showing three primary entities and their immediate dependencies.
Here is more detail about the standard visual elements of a map:
Icon | Description |
|---|---|
Large, hollow hexagon | The primary entities that are the focus of the current map. For example, for a distributed trace or Incident Intelligence issue, those would be the entities directly involved. If the entity is monitored by a New Relic agent, its language or type is indicated by the icon inside the hexagon. |
Small, solid hexagon | Other New Relic-monitored entities that call or are called by the primary entities. |
Cloud | Externals called by the primary entities. |
Database | Datastores called by the primary entities. |
Health status
Some maps use our standard health status colors to indicate entity health.
Distributed trace maps use these colors to indicate health:
- A solid red hexagon means one or more span errors.
- A solid orange hexagon means one or more anomalous spans.
Map tooltip
Maps in context show additional information about map elements when you hover over them.
When you mouse over an entity on a map, you'll see more detail.
The map tooltip includes:
- entity name and type
- any essential tags present on the entity
- golden signals from the last 30 minutes
- hosts the entity is running on, if known
- other entities that have manually-created relationships to this entity
- a link to an entity's mini-overview
- a link to show all of the entity's dependencies
How map relationships are determined
The feature that the map resides in determines the detected relationships. Examples:
- Applied Intelligence: when you select an issue in the UI, the map relies on entity relationships.
- Distributed tracing: when you view a trace in the UI, the map shows the relationships found in the trace.