As a Full platform user, you can use NRQL to directly query entity and relationship data in NRDB alongside your telemetry data. This unified access supports troubleshooting and system analysis.
This document covers the following topics:
- Querying entity and relationship data with NRQL
- Correlating entities with telemetry for comprehensive analysis
- Exploring practical examples, such as tracking state changes and finding application-host relationships
Key benefits
We've centralized your data by bringing entities and their relationships directly into NRDB. This means you can use NRQL to query entity data, relationship data, and telemetry together in a single place.
Here's how you benefit:
- Access all your entity data directly in NRDB: NRDB ingests and stores your entity and relationship data. This creates a unified datastore, making it the central place for this critical information alongside your telemetry data.
- Query entity data using familiar NRQL: You can use the NRQL you're already familiar with to query this entity and relationship data. You don't need to learn new query languages or perform complex joins across different data stores.
- Analyze entity data within its 24-hour retention window: NRDB retains this entity and relationship data for 24 hours, so you can perform timely analysis and retrieve the information needed to understand system behavior and identify dependencies.
중요
Entity relationship data is retained for 24 hours.
- Correlate entities, relationships, and telemetry in a single query: You can link entities, their relationships, and your associated telemetry data (like metrics, events, logs, and traces). This correlation capability lets you connect entity health, relationships, and performance data in a single query.
Next steps
See our NRQL query examples for entities and relationships for practical queries covering common use cases like correlating CPU usage with host attributes, tracking entity state changes, and finding applications related to hosts.