New Relic Verified Foundation flashcards
New Relic Verified Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Apdex score formula
- Apdex = (satisfied responses + tolerating responses / 2) / total responses, where satisfied is at or below threshold T and tolerating is at or below 4T. Scores run from 0 to 1.
- Transaction vs segment
- A transaction is one logical unit of work such as a web request or background job. Segments are the timed spans within it, such as database calls or external requests, used to break down response time.
- Distributed tracing purpose
- Distributed tracing links spans across services and hosts using trace headers, producing a single trace that shows the full call path, per-span duration, and which downstream service caused delay.
- Errors Inbox function
- Errors Inbox aggregates error events by fingerprint, letting teams group, assign, and triage errors rather than reviewing individual occurrences. Error profiles summarize stack traces across many occurrences.
- Throughput and error rate
- Throughput is reported in requests per minute, and error rate as the percentage of failed transactions. Percentile response times (median, 95th, 99th) reveal tail latency that averages conceal.
- Browser agent modes
- The full browser agent captures page load timing, AJAX calls, JavaScript errors, and session data. The Lite agent is a smaller snippet limited to core page-load timing with less overhead.
- Core Web Vitals set
- Core Web Vitals are Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness (replacing First Input Delay), and Cumulative Layout Shift for visual stability.
- Session replay use
- Session replay records sampled user sessions including DOM changes, clicks, and navigation. Replays can be correlated with JavaScript errors and network requests to reproduce reported problems.
- Synthetic monitor types
- Synthetic monitoring offers simple ping checks, browser monitors that run scripted user journeys with screenshots, and scripted API monitors that validate endpoint responses. Public or private minions run them.
- Page load timing phases
- Browser page load timing splits into network, backend, DOM processing, and page rendering phases. The agent reports these as PageView events, with PageAction events capturing user interactions.
- Mobile monitoring coverage
- Mobile monitoring uses iOS and Android SDKs to capture crashes, handled exceptions, HTTP requests, and mobile vitals such as app launch time, tied to backend services through distributed tracing.
- New Relic AI assistant
- The AI assistant answers natural-language questions about your telemetry, generates NRQL, and explains results. It is scoped to the user's existing permissions and cannot access data the user cannot query.
- Anomaly detection baselines
- Applied Intelligence anomaly detection learns a baseline from historical metric behavior instead of using static thresholds, reducing noise for seasonal or spiky data. It can be selected per alert condition.
- AI-assisted root cause
- AI-driven alerting groups related incidents and surfaces probable root-cause signals across linked entities, complementing user-defined alert policies and thresholds.
- Deployment markers correlation
- Change tracking and deployment markers record releases and configuration changes, letting AI-assisted analysis and dashboards correlate performance shifts with recent deployments.
- AI feature availability
- AI features depend on account tier, feature flags, region, and data-privacy settings. Availability can differ between accounts, so confirm current entitlements before relying on a capability.
- Infrastructure agent role
- The infrastructure agent runs on Linux and Windows hosts and collects CPU, memory, disk, and network metrics. On-host integrations add service-specific metrics such as database or web server statistics.
- Cloud integrations polling
- Cloud integrations for AWS, Azure, and GCP poll provider APIs or metric streams to collect service metrics such as EC2, RDS, and Lambda without installing an agent on each resource.
- Kubernetes monitoring stack
- Kubernetes monitoring combines the Kubernetes integration for cluster, node, pod, and workload metrics with Pixie for eBPF-based data and events, all tied into the entity model.
- Infrastructure sample event types
- Infrastructure data is queryable via NRQL event types including SystemSample for hosts, StorageSample for disks, NetworkSample for interfaces, and ProcessSample for running processes.
- Host not reporting condition
- A host not reporting alert condition fires when an agent stops sending data, detecting silent failures. Entity health status rolls up alert state from all attached conditions.
- Log ingestion paths
- Logs enter New Relic through the infrastructure agent's log forwarding, the log API, or third-party forwarders. Parsed attributes become queryable fields on Log events.
- Log parsing rules
- Log parsing rules transform raw messages into structured attributes, such as extracting status codes or timestamps, so the fields can be filtered and faceted in NRQL queries.
- Logs in context
- Logs in context links application logs to APM entities using attributes such as entity.guid, trace.id, and span.id, enabling navigation from a trace directly to related log lines.
- Log patterns clustering
- Log patterns cluster similar messages into groups, surfacing new or unusually high-volume patterns without writing per-message queries. Useful for spotting novel errors during incidents.
- Log data partitions
- Data partitions control which log data is stored and for how long. Partitions with longer retention cost more per GB, so retention is a pricing decision separate from ingest volume.
- NRQL query structure
- NRQL queries follow SELECT ... FROM event type with optional WHERE, FACET, TIMESERIES, and LIMIT clauses. Functions include average(), percentile(), count(), and rate().
- Alert policy components
- Alerts consist of policies, conditions, and notification destinations. Workflows route resulting issues to destinations such as email, Slack, PagerDuty, or webhooks.
- Workloads grouping
- Workloads group related entities so health and alerts can be viewed and targeted at a business-service level rather than per individual resource or host.
- NerdGraph API
- NerdGraph is New Relic's GraphQL API for querying and configuring the platform programmatically. REST APIs and Terraform tooling complement it for automation and configuration as code.
- Usage-based pricing model
- New Relic charges primarily by ingested data volume per GB plus per-user pricing, rather than per host. The Free tier includes a monthly data allowance and one full user.
- Data type pricing
- Ingest is priced by data type, such as APM events, infrastructure metrics, logs, and browser data. Shifting data between types can change cost even at equal total volume.