Use New Relic One's Dependencies page in the Entity explorer to view a filterable list of all the applications, services, databases, and hosts connected to the entity. It shows up and downstream dependencies, and provides paths to explore them.
Similar to service maps, the dependencies page helps you understand how all of your upstream and downstream services are connected. It also uses the same color coding system in service maps to show you what's performing well and what isn't.
To view an entity's dependencies in New Relic One, make sure your app uses the minimum required APM agent version:
- C 1.0.0 or higher
- Go 1.11 or higher
- Java 3.9.0 or higher
- .NET 4.2 or higher
- Node.js 2.0.0 or higher
- PHP 4.19.0 or higher
- Python 18.104.22.168 or higher
- Ruby 4.3.0 or higher
To view dependencies for applications, services, databases, and hosts connected to an entity:
- Go to one.newrelic.com > Entity explorer > (select an entity).
- Select Dependencies.
- To drill down further, filter the apps, services, databases, or hosts.
You can filter the dependencies page to view specific things that report to the entity. Dependencies include:
- Services: applications and services monitored by New Relic APM.
- Mobile applications: apps monitored by New Relic Mobile.
- Browser applications: apps monitored by New Relic Browser.
- External services: external services monitored by APM. External services include out-of-process services such as web services, resources in the cloud, and any other network calls.
- Databases: your application's database and cache data. Databases are agentless. Because of this, alerts cannot be set for the database, as only the service call is reported to New Relic.
- Hosts: servers and hosts monitored by New Relic Infrastructure.