| title | metaDescription |
|---|---|
Product and capabilities: capitalization, trademarks, and usage |
Use these guidelines for all content types, including New Relic UI. |
import styleguideNewRelicProductNamingHierarchy from 'images/style-guide_diagram_new-relic-product-naming-hierarchy.webp'
This page is the definitive resource for capitalizing products, features, and capabilities for use by all New Relic content creators. These guidelines have been vetted by members of legal, content and product marketing, and docs, as well as leaders from around New Relic. Visit the word-nerds slack channel if you have questions about or additions to the list.
In general, we use title case for our company name, product/platform name, and a few capabilities and integrations that require it for legal reasons. The following sections also call out first and subsequent uses of terms. First use refers to the first mention in the body copy. It's okay to use the subsequent versions in space-constrained areas such as titles, headers, tables, web navigation, the UI, social media posts, and so on.
Do not use acronyms specific to or coined by New Relic externally; only use industry-recognized acronyms such as APM externally.
Find capitalization guidelines for [user types](/docs/style-guide/word-choice/user-related-language-guidelines#styles) and [product editions](/docs/style-guide/word-choice/pricing-language-guidelines#style-format).A trademark is a word, name, symbol, or a combination of the three that identifies a particular product or service. A trademark is how customers recognize you in the marketplace and distinguish you from your competitors for those goods and services.
A trademark name is the name of a company conducting business. The New Relic trademark name is New Relic, Inc.
Here are the general trademark guidelines when using the New Relic brand name:
- Do not make New Relic or its platform, capabilities, and so on possessive using apostrophes. For example, use “New Relic platform functions” or “New Relic functionality” instead of “New Relic's platform functions” or “New Relic's functionality.”
- Do not pluralize New Relic or its platform, capabilities, and so on.
- Do not abbreviate or combine New Relic or its platform, capabilities, and so on.
- Do not hyphenate New Relic or its platform, capabilities, and so on, and do not allow them to break across a page line when used in text.
- Avoid confusion by clearly separating and identifying New Relic trademarks from other companies' names and/or trademarks.
Note that it’s generally a best practice to apply these trademark guidelines to other companies’ trademarked names and products too, unless the company’s trademark policies require a different approach.
It’s not necessary to use trademark characters after product names in headings and text on newrelic.com webpages.
In general, it’s not necessary or recommended to use trademark characters after third-party product names on newrelic.com webpages or documents (including PDFs). New Relic is typically not in the position to know if a particular mark is registered. Assuming a third-party product name or other third-party mark is registered can lead to unintended and undesired consequences for New Relic. Thus, avoid using the ® or ™ symbol unless a third party that New Relic partners or works with specifically requires the use of the symbol as a part of its trademark policy.
In some instances, a third party requires the use of the ® or ™ symbol by contract or through its trademark policy. For example, LEGO. A recent FutureStack event promoted an activity in which a LEGO master would create a LEGO model. In this case, LEGO required that the first occurrence of LEGO in New Relic copy should be followed by ®. For example, "You can win a one-of-a-kind LEGO® model of the New Relic Data Nerd Knuckles."
If a company we're working with has its trademark policy publicly available or has privately provided the policy to New Relic, please consult that policy and follow the company’s policy for use of the ® or ™ symbol. If you're unsure of whether you need to acknowledge a third-party trademark in your copy, contact Legal in the #suplegal channel in Slack.
You must use title case for our trademarked names including our company name plus our product/platform name and a few capability and integration names.
This table is kept up to date and is the source of truth for capitalization. Most capability and feature names are lowercase because New Relic is one platform. However, some terms and capabilities are capitalized for trademark or pricing reasons. Note that the use of "capability" here is different than our use of that word in the user management space.
<th>
What it is
</th>
<th className="fcenter">
<Icon style={{color: 'green'}} name="fe-check"/> Use this
</th>
<th className="fcenter">
<Icon style={{color: 'red'}} name="fe-x-circle"/> Not this
</th>
</tr>
<td>
our company
</td>
<td>
First use: New Relic, Inc. (corporation/entity), New Relic<sup>®</sup> (printed assets), or New Relic (digital assets)
Subsequent uses: New Relic, our company, we, or it
</td>
<td>
Do not use: New Relic's, new relic, New relic, NR, their
</td>
</tr>
<tr>
<td>
New Relic platform
</td>
<td>
our product/platform
</td>
<td>
First use: New Relic (docs, UI, titles) or New Relic observability platform (marketing content)
Subsequent uses: New Relic or New Relic platform
Note: New Relic observability platform is recommended for marketing content where users might not be familiar with our product.
</td>
<td>
Do not use: New Relic's, New Relic One, NR1
</td>
</tr>
<tr>
<td>
FutureStack\*
{Future}Stack\*
</td>
<td>
our annual user group conference
</td>
<td>
First use: FutureStack<sup>®</sup> or {Future}Stack<sup>®</sup> (printed assets), or FutureStack or {Future}Stack (digital assets)
Subsequent uses: FutureStack
</td>
<td>
Do not use: Future Stack, Futurestack, Future stack
</td>
</tr>
<tr>
<td>
NerdGraph\*
</td>
<td>
our GraphQL API
</td>
<td>
First use: NerdGraph<sup>®</sup> (printed assets) or NerdGraph (digital assets)
Subsequent uses: NerdGraph
</td>
<td>
Do not use: Nerd Graph, Nerdgraph, nerdgraph, nerd graph
</td>
</tr>
<tr>
<td>
Nerdlet\*
</td>
<td>
component of New Relic apps; a specific UI view represented by a React JavaScript package
</td>
<td>
First use: Nerdlet<sup>®</sup> (printed assets) or Nerdlet (digital assets)
Subsequent uses: Nerdlet
</td>
<td>
Do not use: nerdlet, NerdLet
</td>
</tr>
<tr>
<td>
Nerdpack\*
</td>
<td>
component of New Relic apps; the package containing all the files needed by that app
</td>
<td>
First use: Nerdpack<sup>®</sup> (printed assets) or Nerdpack (digital assets)
Subsequent uses: Nerdpack
</td>
<td>
Do not use: nerdpack, NerdPack, Nerd Pack, nerd pack
</td>
</tr>
<tr>
<td>
NerdStorage\*
</td>
<td>
component of New Relic apps; used to store and retrieve simple sets of data
</td>
<td>
First use: NerdStorage<sup>®</sup> (printed assets) or NerdStorage (digital assets)
Subsequent uses: NerdStorage
</td>
<td>
Do not use: Nerdstorage, nerdstorage, Nerd Storage, Nerd storage, nerd storage
</td>
</tr>
<td>
our generative AI observability assistant
</td>
<td>
The product is New Relic AI, and that's how we want to present it.
* First use: New Relic AI
* Subsequent uses: New Relic AI. You can also use "our GenAI" or “our GenAI assistant” if the text is lengthy and consistent use of the term New Relic AI becomes redundant.
</td>
<td>
Do not use: NR AI, New Relic Grok, or AI. In general, only refer to AI when talking generally about the concept of AI, but never to refer to one of our products.
Note: There are other AI tools not associated with New Relic. For these, always specify the company name to ensure readers understand that we're not referring to New Relic AI.
</td>
</tr>
<td>
New Relic pricing model based on compute capacity consumed instead of host or individual user licenses
</td>
<td>
First use: New Relic Compute
Subsequent uses: New Relic Compute or Compute
</td>
<td>
Do not use: compute (when referring to New Relic Compute), NRC
</td>
</tr>
<td>
our all-in-one data option with capabilities for Federal Risk and Authorization Management Program (FedRAMP), extended retention, configurable logs obfuscation rules, cloud provider choice, and more
</td>
<td>
First use: New Relic Data Plus
Subsequent use: Data Plus
</td>
<td>
Do not use: data plus, NRDP, DP
</td>
</tr>
<tr>
<td>
New Relic Explorer
</td>
<td>
former capability of New Relic
</td>
<td>
The New Relic main landing page where users can see and explore monitored entities and access **Lookout** and **Navigator**. In the platform, it's referred to as the **All entities** UI page. We can refer to it as the [entity explorer](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts#find), or the entity list view, or in other informal ways (for example: "the first page you see when you open New Relic").
</td>
<td>
Do not use: New Relic Explorer or Explorer. This is an end-of-life name and should no longer be used in New Relic docs or marketing materials.
</td>
</tr>
<tr>
<td>
New Relic Infinite Tracing\*
</td>
<td>
our fully-managed, tail-based, distributed tracing solution
</td>
<td>
First use: New Relic Infinite Tracing<sup>®</sup> (printed assets) or New Relic Infinite Tracing (digital assets)
Subsequent uses: Infinite Tracing
</td>
<td>
Do not use: Infinite tracing, infinite tracing, New Relic Edge with Infinite Tracing
</td>
</tr>
<tr>
<td>
New Relic Instant Observability
</td>
<td>
ecosystem of quickstarts for New Relic
</td>
<td>
First use: New Relic Instant Observability or New Relic Instant Observability (I/O)
Subsequent uses: Instant Observability or New Relic I/O (avoid using the acronym externally, if possible)
</td>
<td>
Do not use: New Relic instant observability, instant observability, NRIO, IO, I/O
</td>
</tr>
<tr>
<td>
New Relic Lookout
</td>
<td>
capability of New Relic
</td>
<td>
First use: New Relic Lookout
Subsequent uses: New Relic Lookout
Describing actions in the UI: **Lookout**
</td>
<td>
Do not use: New Relic Lookout's, Lookout (okay when directing what to select in the UI), lookout
</td>
</tr>
<tr>
<td>
New Relic Navigator
</td>
<td>
capability of New Relic
</td>
<td>
First use: New Relic Navigator
Subsequent uses: New Relic Navigator
Describing actions in the UI: **Navigator**
</td>
<td>
Do not use: New Relic Navigator's, Navigator (okay when directing what to select in the UI), navigator
</td>
</tr>
<td>
query language similar to ANSI SQL; used to to create queries or run calculations to retrieve detailed New Relic data and get insight into applications, hosts, and business
</td>
<td>
First use: New Relic Query Language (NRQL)
Subsequent uses: NRQL or New Relic Query Language
</td>
<td>
Do not use: New Relic query language, or NRQL on first occurrence
</td>
</tr>
<tr>
<td>
New Relic Vulnerability Management
</td>
<td>
add-on capability of New Relic; used to aggregate vulnerabilities and display them for observability and remediation. (As of January 2023, Vulnerability Management is title case.)
</td>
<td>
- When writing about the activity of managing vulnerabilities: vulnerability management
- When referring to the capability on first mention in body copy: New Relic Vulnerability Management
- When referring to the capability in headings or on subsequent mentions in body copy:
Vulnerability Management
</td>
<td>
Do not use: VM, vulnerability management monitoring, vulnerability monitoring
</td>
</tr>
| Name |
|---|
| New Relic\* |
| New Relic AI (formerly, New Relic Grok) |
|
New Relic AI monitoring (formerly, New Relic AIM or AIM)
Note: For more information, see our blog, Introducing New Relic AI monitoring, the industry’s first APM for AI |
| New Relic Compute |
| New Relic Data Plus |
| New Relic Query Language |
* Trademarked
- New Relic is a registered trademark of New Relic, Inc. It was founded in 2008. We call our employees Relics.
- The New Relic support team can answer all of your questions about New Relic. They're happy to help.
- The New Relic observability platform lets you ingest data from practically any source. New Relic gives you access to our curated UI experiences like application performance monitoring, , mobile monitoring, and more.
- Optimize code performance and feature planning with access to telemetry data from production and pre-production environments directly in your IDE via the New Relic CodeStream integration.
- New Relic Infinite Tracing is a fully managed, cloud-based solution. Infinite Tracing can analyze 100% of your trace data and choose the most actionable data.
Do not capitalize our capability and feature names (what you get with our platform) unless they begin a sentence (and then only capitalize the first word) or are included in the table above. If a capability or feature name includes the name of a trademarked product, then only capitalize the trademarked name (for example, Pixie or Kubernetes).
Feature and capability defined:
- A feature is an individual experience or element of functionality in the New Relic platform or a New Relic capability.
- A capability is a collection of features that enable a customer to achieve a use case. A capability is considered a superset of features and often tends to be an outside-in term that customers associate with an existing category such as application performance monitoring, applied intelligence, infrastructure monitoring, and . In other words, capabilities are the things we'd treat as SKUs if we sold them all separately.
Notes about features and capabilities:
- These are largely internal terms used so that we can discuss New Relic and its structure more clearly. For public resources, we should attempt to avoid these terms and their distinctions and simply talk about how something works.
- Note that this use of “capability” is different from how we define “capability” in the user management space.
View a diagram of the relationship between our product, features, and capabilities.
<th>
What it is
</th>
<th className="fcenter">
<Icon style={{color: 'green'}} name="fe-check"/> Use this
</th>
<th className="fcenter">
<Icon style={{color: 'red'}} name="fe-x-circle"/> Not this
</th>
</tr>
<td>
capability of New Relic; detection and notification of issues
</td>
<td>
alerts
</td>
<td>
Do not use: Alerts
</td>
</tr>
<tr>
<td>
agent
</td>
<td>
installable software used in monitoring; see [Usage dictionary # agent](/docs/style-guide/word-choice/usage-dictionary/#agent) and [Glossary # agent](/docs/new-relic-solutions/get-started/glossary/#agent) for more info.
</td>
<td>
agent
</td>
<td>
Do not use: Agent
</td>
</tr>
<td>
capability of New Relic that uses AI to track IT operations; it uses AI to analyze data generated by software systems, predict possible problems, determine the root cause, and drive automated fixes; "AI" refers to both a New Relic capability and a generic term
</td>
<td>
First use: if space permits, artificial intelligence for IT operations (AIOps); if space does not permit, AIOps
Subsequent uses: AIOps
</td>
<td>
Do not use: AI for IT Ops
</td>
<tr>
<td>
anomaly detection
</td>
<td>
feature of the applied intelligence capability in New Relic that helps distinguish between typical and atypical system performance
</td>
<td>
anomaly detection
</td>
<td>
Do not use: Anomaly Detection, Anomaly detection
</td>
</tr>
<tr>
<td>
application performance monitoring
</td>
<td>
capability of New Relic; using real-time data to track the uptime and reliability of an application
</td>
<td>
First use: application performance monitoring (APM)
Subsequent uses: application performance monitoring, APM, or application monitoring
</td>
<td>
Do not use: Application Performance Management, Application Performance Monitoring, Application Monitoring
</td>
</tr>
<tr>
<td>
applied intelligence
</td>
<td>
capability of New Relic; our AIOps solution; machine learning engine that reduces alert noise, correlates incidents, and automatically detects anomalies
</td>
<td>
applied intelligence
</td>
<td>
Do not use: Applied Intelligence, Applied intelligence, AI, AIOps
</td>
</tr>
<tr>
<td>
automap
</td>
<td>
feature of New Relic; automatically displays relationships between entities in topology view
</td>
<td>
automap
</td>
<td>
Do not use: auto map, Auto Map, Auto map
</td>
</tr>
<tr>
<td>
auto-telemetry with Pixie
</td>
<td>
Pixie integration with New Relic
</td>
<td>
First use: auto-telemetry with Pixie
Subsequent uses: auto-telemetry with Pixie, the Pixie integration with New Relic, our Pixie integration, or the integration with Pixie
</td>
<td>
Do not use: Pixie (okay if referring to px.dev and the open-source Pixie project), Pixie's, Auto-telemetry with Pixie
</td>
</tr>
<tr>
<td>
browser monitoring
</td>
<td>
capability of New Relic; our real-user monitoring (RUM) solution along with mobile monitoring
</td>
<td>
browser monitoring
</td>
<td>
Do not use: Browser Monitoring, Browser monitoring
</td>
</tr>
<tr>
<td>
code-level metric(s)
</td>
<td>
feature of the New Relic CodeStream capability that allows you to see the golden signals (throughput, error rate, response rate) at the method level within your code.
</td>
<td>
code-level metric or code-level metrics
</td>
<td>
Do not use: code level metric(s), Code-Level Metric(s), Code-level Metric(s), Code-level metric(s) (unless at the beginning of a sentence), CLM
</td>
</tr>
<td>
New Relic Compute is measured in compute capacity units (CCUs), representing the capacity consumed to complete a successfully run customer-initiated action
</td>
<td>
First uses: compute capacity unit (CCU) or compute capacity units (CCUs). Note: For contractual, licensing, and legal docs, use "Compute Capacity Unit (CCU)" or "Compute Capacity Units (CCUs)."
Subsequent uses: CCU or CCUs
</td>
<td>
Do not use: Compute Capacity Unit
</td>
</tr>
<tr>
<td>
containers
</td>
<td>
a method to package software for release
</td>
<td>
containers
</td>
<td>
Do not use: Containers
</td>
</tr>
<tr>
<td>
dashboards
</td>
<td>
capability of New Relic that uses NRQL to build custom visualizations
</td>
<td>
dashboards
</td>
<td>
Do not use: Dashboards
</td>
</tr>
<tr>
<td>
data ingest
</td>
<td>
bringing metrics, events, logs, and traces (MELT) data into New Relic
</td>
<td>
data ingest
</td>
<td>
Do not use: Data Ingest, Data ingest
</td>
</tr>
<tr>
<td>
digital experience monitoring
</td>
<td>
a combo of New Relic frontend monitoring capabilities (browser, mobile, synthetics)
</td>
<td>
First use: digital experience monitoring (DEM)
Subsequent uses: digital experience monitoring or DEM
</td>
<td>
Do not use: Digital Experience Monitoring, Digital experience monitoring, digital monitoring
</td>
</tr>
<tr>
<td>
distributed tracing
</td>
<td>
feature of New Relic; a solution for observing service requests as they flow through a distributed system
</td>
<td>
distributed tracing
</td>
<td>
Do not use: Distributed Tracing, Distributed tracing
</td>
</tr>
<tr>
<td>
errors inbox
</td>
<td>
capability of New Relic; our error tracking solution for triaging and resolving full-stack errors
</td>
<td>
errors inbox
</td>
<td>
Do not use: Errors Inbox, Errors inbox
</td>
</tr>
<tr>
<td>
event correlation
</td>
<td>
feature of the applied intelligence capability in New Relic that automatically groups alerts to decrease noise
</td>
<td>
event correlation
</td>
<td>
Do not use: Event Correlation, Event correlation
</td>
</tr>
<tr>
<td>
incident intelligence
</td>
<td>
feature of the applied intelligence capability in new Relic that correlates incidents and offers suggested responders
</td>
<td>
incident intelligence
</td>
<td>
Do not use: Incident Intelligence, Incident intelligence
</td>
</tr>
<tr>
<td>
infrastructure monitoring
</td>
<td>
capability of New Relic that collects performance data on hosts and servers (IT infrastructure) to understand health
</td>
<td>
First use: infrastructure monitoring
Subsequent uses: infrastructure monitoring, infra monitoring, or infra (for space-constrained areas only)
</td>
<td>
Do not use: Infrastructure Monitoring, Infrastructure monitoring
</td>
</tr>
<tr>
<td>
integrations
</td>
<td>
solutions that integrate with/gather data from third parties; all our integrations can be found as quickstarts in New Relic Instant Observability
</td>
<td>
integrations
</td>
<td>
Do not use: Integrations
</td>
</tr>
<tr>
<td>
interactive application security testing
</td>
<td>
capability of New Relic that's fully integrated with New Relic Vulnerability Management to continuously find, fix, and verify high-risk vulnerabilities across the software developer lifecycle (SDLC)
</td>
<td>
First use: New Relic interactive application security testing (IAST)
Subsequent uses: interactive application security testing or IAST
</td>
<td>
Do not use: New Relic Interactive Application Security Testing or Interactive Application Security Testing
</td>
</tr>
<tr>
<td>
Kubernetes cluster explorer
</td>
<td>
feature of the Kubernetes monitoring capability that provides a multi-dimensional representation of a Kubernetes cluster and enables teams to drill down into Kubernetes data
</td>
<td>
Kubernetes cluster explorer
</td>
<td>
Do not use: Kubernetes Cluster Explorer, kubernetes cluster explorer
</td>
</tr>
<tr>
<td>
Kubernetes monitoring
</td>
<td>
capability of New Relic; form of reporting that helps with proactive management of clusters
</td>
<td>
Kubernetes monitoring
</td>
<td>
Do not use: Kubernetes Monitoring, kubernetes monitoring
</td>
</tr>
<tr>
<td>
log management
</td>
<td>
capability of New Relic; collecting, formatting, and analyzing log data to optimize systems
</td>
<td>
First use: log management
Subsequent uses: log management or logs
</td>
<td>
Do not use: Log Management, Log management, Logs
</td>
</tr>
<tr>
<td>
logs in context
</td>
<td>
feature of the log management capability in New Relic; tracing logs throughout a complex service
</td>
<td>
logs in context
</td>
<td>
Do not use: Logs in Context, Logs in context
</td>
</tr>
<tr>
<td>
metrics and events
</td>
<td>
feature of New Relic; navigating data in New Relic without NRQL know-how
</td>
<td>
metrics and events
</td>
<td>
Do not use: Metrics and events
</td>
</tr>
<tr>
<td>
metrics, events, logs, and traces
</td>
<td>
what you monitor for full-stack observability
</td>
<td>
First use: metrics, events, logs, and traces or metrics, events, logs, and traces (MELT)
Subsequent uses: metrics, events, logs, and traces or MELT
</td>
<td>
Do not use: Metrics, Events, Logs, and Traces
</td>
</tr>
<td>
New Relic capability that monitors machine-learning (ML) models in production; our monitoring solution for MLOps (machine-learning operations)
</td>
<td>
machine learning (ML) model performance monitoring
</td>
<td>
Do not use: Model Performance Monitoring, Model performance monitoring, ML model monitoring, ML model performance monitoring, MPM
</td>
</tr>
<td>
a set of practices designed to increase the quality, simplify the management process, and automate the deployment of machine-learning models in large-scale production environments
</td>
<td>
First use: if space permits, machine-learning operations (MLOps); if space does not permit, MLOps
Subsequent uses: MLOps, ML ops
</td>
<td>
Do not use: ML Ops, ML ops
</td>
<tr>
<td>
microservices
</td>
<td>
modern application architecture (vs. monolith)
</td>
<td>
microservices
</td>
<td>
Do not use: micro services, Micro Services, Microservices
</td>
</tr>
<tr>
<td>
mobile monitoring
</td>
<td>
capability of New Relic; our RUM solution along with browser monitoring
</td>
<td>
mobile monitoring
</td>
<td>
Do not use: Mobile Monitoring, Mobile monitoring
</td>
</tr>
<tr>
<td>
monitoring
</td>
<td>
Use monitoring when you're describing specific capabilities and the data from those capabilities. (For more information, see [Usage dictionary: Observability vs. monitoring](/docs/style-guide/word-choice/usage-dictionary/#observability-monitoring).)
</td>
<td>
First use: monitoring
New Relic capabilities that include monitoring in the name are also lowercase; for example, application performance monitoring, browser monitoring, and infrastructure monitoring.
</td>
<td>
Do not use: Monitoring, observability
</td>
</tr>
<tr>
<td>
network performance monitoring
</td>
<td>
capability of New Relic; understanding how a network is experienced by users
</td>
<td>
First and subsequent uses: network monitoring
</td>
<td>
Do not use: Network Performance Monitoring, Network performance monitoring, Network Monitoring, Network monitoring
</td>
</tr>
<tr>
<td>
observability
</td>
<td>
In general, use observability to describe the New Relic platform and the health of a system holistically based on different types of data. Observability is using the outputs of a system, including different types of data, to understand its health, enabling engineers to gain insights and diagnose issues effectively. (For more information, see [Usage dictionary: Observability vs. monitoring](/docs/style-guide/word-choice/usage-dictionary/#observability-monitoring).)
</td>
<td>
First use: observability, full-stack observability, end-to-end observability, New Relic observability platform
Subsequent uses: o11y (derived from removing the 11 letters between the “o” and the “y” in “observability”; note that it’s two number “1”s and not two letter “l”s)
</td>
<td>
Do not use: Observability, Full-Stack Observability, Full-stack Observability, Full-stack observability, monitoring
</td>
</tr>
<tr>
<td>
query, queries, querying
</td>
<td>
feature of New Relic; NRQL- or Prom-QL-style way of asking bespoke questions of data
</td>
<td>
query, queries, or querying
</td>
<td>
Do not use: Query, Queries, Querying
</td>
</tr>
<tr>
<td>
query builder
</td>
<td>
feature of New Relic; previously known as chart builder
</td>
<td>
query builder
</td>
<td>
Do not use: Query Builder, Query builder
</td>
</tr>
<tr>
<td>
quickstarts
</td>
<td>
feature of New Relic Instant Observability; pre-built open-source integrations that include dashboards and alerts
</td>
<td>
quickstarts
</td>
<td>
Do not use: quick starts, Quick Starts, QuickStarts, Quickstarts
</td>
</tr>
<tr>
<td>
real user monitoring
</td>
<td>
see [Usage dictionary # Real user monitoring](/docs/style-guide/word-choice/usage-dictionary/#real-user-monitoring)
</td>
<td>
First use: real user monitoring (RUM)
Subsequent use: RUM
</td>
<td>
Do not use: real-user-monitoring, real-user monitoring, Real User Monitoring, Real-User-Monitoring, Real-User Monitoring
</td>
</tr>
<tr>
<td>
serverless monitoring
</td>
<td>
capability of New Relic for Lambda and serverless functions
</td>
<td>
serverless monitoring
</td>
<td>
Do not use: Serverless Monitoring, Serverless monitoring
</td>
</tr>
<tr>
<td>
service levels
</td>
<td>
feature of New Relic; used to measure the performance of a service
</td>
<td>
service level or service levels
</td>
<td>
Do not use: Service Levels, Service levels, SL, services levels, Services Levels
</td>
</tr>
<tr>
<td>
service maps
</td>
<td>
feature of New Relic; visual representation of a service
</td>
<td>
service maps
</td>
<td>
Do not use: Service Maps, Service maps
</td>
</tr>
<tr>
<td>
synthetic monitoring
</td>
<td>
capability of New Relic; simulating users across geographies to identify bottlenecks or experience issues; aka synthetic tests for APIs or browsers
</td>
<td>
First use: synthetic monitoring
Subsequent uses: synthetic monitoring or synthetics or synthetic monitors
</td>
<td>
Do not use: synthetics monitoring, Synthetic Monitoring, Synthetic monitoring
</td>
</tr>
<tr>
<td>
workloads
</td>
<td>
feature of New Relic; used to aggregate the health and activity of all entities that provide a business logic
</td>
<td>
workload or workloads
</td>
<td>
Do not use: Workloads, work loads, Work Loads, Work loads
</td>
</tr>
| Name |
|---|
| alerts |
| AIOps (artificial intelligence for IT operations) |
| compute capacity unit |
| machine learning (ML) model performance monitoring |
| MLOps (machine-learning operations) |
If you don't see a feature or capability in one of the above tables, assume that it is not capitalized.
- Application performance monitoring (APM) helps you instantly understand application performance, dependencies, and bottlenecks. APM gives you a complete view of your applications and operating environment.
- Covered entities can now send application, infrastructure, digital experience, and network monitoring data to New Relic while maintaining HIPAA compliance.
- When you need to correlate log data with other telemetry data, enable logs in context in New Relic.
- NRQL is a query language you can use to query the New Relic database.
- With a quickstart, you can quickly install dashboards, alerts, and other resources.
We used to capitalize our platform components (below). However, we no longer position our platform this way. Check out how we're positioning our platform and the recommendations for how to refer to these platform components in the following table.
<th>
What it is
</th>
<th className="fcenter">
<Icon style={{color: 'green'}} name="fe-check"/> Use this
</th>
<th className="fcenter">
<Icon style={{color: 'red'}} name="fe-x-circle"/> Not this
</th>
</tr>
<td>
formerly a separate product—now a capability of New Relic
</td>
<td>
applied intelligence
</td>
<td>
Do not use: Applied Intelligence, AI, AIOps
</td>
</tr>
<tr>
<td>
Full-Stack Observability
</td>
<td>
formerly a separate product—now in lowercase, it describes an outcome of using New Relic
</td>
<td>
full-stack observability
</td>
<td>
Do not use: Full-Stack Observability, Full-stack Observability, Full Stack Observability, full stack observability, FSO
</td>
</tr>
<tr>
<td>
Telemetry Data Platform
</td>
<td>
formerly a separate product—now part of New Relic
</td>
<td>
telemetry data platform (avoid this term altogether when possible)
</td>
<td>
Do not use: Telemetry Data Platform, Telemetry data platform, TDP
</td>
</tr>
| Name |
|---|
| Applied Intelligence |
- Engineers can use applied intelligence to detect, diagnose, and mitigate problems more quickly and easily.
- A set of dashboards with data from all New Relic products gives you full-stack observability of your metrics, events, logs, and traces.
Downloadable or printable New Relic documents that are available to the public require a copyright disclaimer in the footer for all registered and unregistered trademarks used within the document. In any instance where the registration marks are not used in downloadable/printable documents, include the following statement in the copyright area of the footer:
© 2008-22 New Relic, Inc. All rights reserved. New Relic and the New Relic logo are registered trademarks of New Relic, Inc. All product and company names herein may be trademarks of their registered owners.
Update the copyright year to reflect the current year.
For purely internal documents, neither the copyright or the trademark notices are required because we are not publishing the documents or putting third parties on notice. Instead, add the following disclaimer to the footer:
New Relic confidential; for internal use only
You should also add the word “internal” to the file name.
This is not an exhaustive diagram, but it provides a model for how our features and capabilities fit together into our product.