Skip to content

feat: Catalog GA docs #21307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

feat: Catalog GA docs #21307

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
edf4684
ga-commit
WriteMayur Jul 23, 2025
ef89560
removed-translation
WriteMayur Jul 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions ...ontent/docs/service-architecture-intelligence/catalogs/applications-catalog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,14 @@ tags:
freshnessValidatedDate: never
---

<Callout title="Preview">
We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
</Callout>
Applications catalog offers a single pane view to enhance the observability and management of entities in your organization. The unified view of Services - APM, Services - OpenTelemetry, Browser, and Mobile entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams.

<Callout variant="important">

Applications catalog offers a single pane view to enhance the observability and management of entities in your organization. The unified view of Services - APM, Services - OpenTelemetry, Browser, and Mobile entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams.
The Applications catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).

</Callout>


### Supported entities [#supported-entities]
Expand Down Expand Up @@ -79,8 +79,8 @@ The <DNT>Application Catalog</DNT> page has multiple columns to displays various
<td>The team responsible for the entity. Click on the team's name to go to the corresponding team's hub page to view more information of team's managing the entity. Hover the mouse to the <DNT>Team</DNT> link to view additional details in the pop-up dialog box. If a Team is not assigned to an entity, click the <DNT>Assign Team</DNT> button and select the responsible team from the displayed list. For more information, refer [Teams](/docs/service-architecture-intelligence/teams/teams). </td>
</tr>
<tr>
<td><DNT>Issues</DNT></td>
<td>The number of active issues created in the <DNT>past 24 hours</DNT>. Hover the mouse to the cell to view a brief overview on those entities' issues. Click the number to view the details. Hover the mouse to the <DNT>Issues</DNT> link to view additional details in the pop-up dialog box. You can also click the links in the pop-up dialog box to open the Alerts. For more information, refer [Alerts](/docs/alerts/overview/) and [Issues](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td>
<td><DNT>Alerts</DNT></td>
<td>The number of active alerts created in the <DNT>past 24 hours</DNT>. Hover the mouse to the cell to view a brief overview on those entities' alerts. Click the link in the pop-up dialog box to view additional details. For more information, refer [Alerts](/docs/alerts/overview/) and [Issues](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td>
</tr>
<tr>
<td><DNT>Last Deploy</DNT></td>
Expand Down
14 changes: 6 additions & 8 deletions src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,19 +6,13 @@ tag:
- "Applications Catalog"
- "Repositories Catalog"
- "Infrastructure Catalog"
- "All in one Catalog"
- 'New Relic Catalogs'
metaDescription: "Catalogs offer a single pane view to enhance the observability and management of software systems in your organization. The unified view of system entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams."
freshnessValidatedDate: never
---


<Callout title="Preview">
We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
</Callout>



New Relic Catalogs provides a single-pane view that enhances the observability and management of systems across your organization. By offering a unified perspective on entities, it empowers teams to make well-informed decisions, streamline operations, and collaborate more effectively.

With Catalogs, you can quickly identify and focus on the most relevant information, ensuring easy access to what matters most. It serves as the single source of truth, enabling users to discover, manage, and optimize their systems with confidence.
Expand Down Expand Up @@ -151,3 +145,7 @@ To go back to the <DNT>Catalogs</DNT> view, click the <DNT>**Try it out**</DNT>
alt="Catalog"
src={CatalogHome}
/> */}

## Pricing [#pricing]

The Catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).
175 changes: 175 additions & 0 deletions ...tent/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,175 @@
---
title: "Infrastructure Catalog"
metaDescription: "Learn how to use the Infrastructure Catalog to manage your infrastructure resources in New Relic."
tag:
- "Service Architecture Intelligence"
- "Catalogs"
- "Applications Catalog"
- "Repositories Catalog"
- "Infrastructure Catalog"
- "All in one Catalog"
- 'New Relic Catalogs'
freshnessValidatedDate: never
---


The Infrastructure Catalog provides a complete inventory of all your infrastructure entities. Use it to manage resources, accelerate root cause analysis, and identify observability gaps. The catalog displays key information for each resource, including high-level details, ownership, configuration data, and its relationships with other resources, applications, and services.

Data is populated automatically from New Relic infrastructure agents and cloud integrations.

<Callout variant="important">

The Infrastructure catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).

</Callout>

## Key features [#key-features]

* **Centralized resource view:** Gain a high-level, cross-account view of your infrastructure resources. Filter and group by attributes like resource category, entity type, region, environment, or team to improve organization and visibility.

* **Application and service mapping:** See which applications and services are running on each compute resource to quickly assess impact and triage issues.

* **Clear ownership and accountability:** Easily identify owners for both infrastructure components and their dependent applications or services. This clarifies accountability when infrastructure issues arise.

* **Actionable resource insights:** Access insights into infrastructure activity—including health status, related incidents, scorecards, and more—to inform your resource optimization efforts.

* **Detailed resource configuration:** Quickly access current configuration data for each resource, enabling faster debugging and reducing context switching.

## Access the Infrastructure catalog [#access-infra-catalog]

The Infrastructure catalog is available in the New Relic platform, providing a comprehensive view of your infrastructure resources. You can use it to manage your resources, accelerate root cause analysis, and identify observability gaps.

**Prerequisites:**

* Enable the Catalogs in your New Relic account. For more information, refer [Enable the Catalogs](https://docs.newrelic.com/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs).

**To access the Infrastructure catalog inventory:**

1. Log in to your New Relic platform.
2. Go to the <DoNotTranslate>left navigation pane > Catalogs > Infrastructure catalog</DoNotTranslate>.

<img
title="Infrastructure catalogs"
alt="An infrastructure catalog view in New Relic"
src="/images/infracatalogs.webp"
/>

The Infrastructure Catalog page displays multiple columns to present various information for an infra resource:

<table>
<thead>
<tr>
<th>UI</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>Name</td>
<td>
The name of the infrastructure entity.
<ul>
<li>Click the entity name to open its Entity Overview page.</li>
<li>Hover over the entity name to view additional details in a pop-up. You can also click links within this pop-up.</li>
</ul>
</td>
</tr>
<tr>
<td>Type</td>
<td>The type of the infrastructure resource. For example, `Host`, `KubernetesCluster`.</td>
</tr>
<tr>
<td>Category</td>
<td>
A high-level grouping of resources. Supported categories include:
<ul>
<li>`AI + ML`</li>
<li>`Analytics`</li>
<li>`Compute`</li>
<li>`Database`</li>
<li>`Networking`</li>
<li>`Other`</li>
<li>`Queues/Streams/Events`</li>
<li>`Security & Identity`</li>
<li>`Storage`</li>
</ul>
</td>
</tr>
<tr>
<td>Cloud</td>
<td>The cloud provider for the entity. It can be `AWS`, `Azure`, `GCP`, or any other. For `Hosts` and `Containers`, the cloud provider is determined by checking the `cloudProvider` tag. For all other entity types, the cloud is automatically identified.</td>
</tr>
<tr>
<td>Score</td>
<td>The percentage of scorecard rules passed by the entity. This value helps you measure how entities are performing against best practices defined in the Scorecards capability. Hover over the score to view a summary. For more information, refer to [Scorecards](https://docs.newrelic.com/docs/service-architecture-intelligence/scorecards/getting-started/).</td>
</tr>
<tr>
<td>Team</td>
<td>
The team responsible for the entity.
<ul>
<li>Click a team name to navigate to that team's page.</li>
<li>Hover over a team name to view additional details.</li>
<li>If a team is not assigned, click Assign Team and select the responsible team.</li>
</ul>
For more information, refer to [Teams](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/teams/).
</td>
</tr>
<tr>
<td>Services</td>
<td>The number of related services and applications running on the infrastructure resource. This data is derived from New Relic entity relationships to help you understand service-to-infrastructure dependencies. Hover over the number to see a list of related services. You can click links in the pop-up to navigate to those services.</td>
</tr>
<tr>
<td>Alerts</td>
<td>The number of active alerts impacting the entity within the last 24 hours. Hover over the cell to see a summary of recent alerts. Click links in the pop-up to view details for each alert. For more information, refer to [Alerts](https://docs.newrelic.com/docs/alerts/overview/) and [Issues](https://docs.newrelic.com/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td>
</tr>
<tr>
<td>Region</td>
<td>The geographic location or cloud provider region where the resource is deployed. This helps you understand data locality, latency, and compliance. The Region value is populated automatically by checking for values across a prioritized list of metadata tags. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary.
The following tags are checked in order:
<ul>
<li>`region`</li>
<li>`cloud.region`</li>
<li>`aws.region`</li>
<li>`awsRegion`</li>
<li>`azure.regionName`</li>
<li>`gcp.region`</li>
</ul>
</td>
</tr>
<tr>
<td>Availability Zone</td>
<td>The isolated location within a cloud region where the resource is deployed. This is used for fault tolerance and high availability by distributing resources across multiple zones. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary.
The following tags are checked in order:
<ul>
<li>`availabilityZone`</li>
<li>`cloud.availability_Zone`</li>
<li>`aws.availabilityZone`</li>
<li>`awsAvailabilityZone`</li>
<li>`azure.availabilityZone`</li>
<li>`gcp.zone`</li>
</ul>
</td>
</tr>
<tr>
<td>Environment</td>
<td>The stage or purpose of the resource in the software lifecycle. For example, `development`, `staging`, or `production`. This helps teams manage stability, testing, and deployment workflows. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary.
The following tags are checked in order:
<ul>
<li>`Environment`</li>
<li>`environment`</li>
<li>`env`</li>
</ul>
</td>
</tr>
</tbody>
</table>

## Add new data [#add-new-data]

To add additional data to your Infrastructure catalog click the + Add Data button at the top right. Follow the on screen instructions to add data to your Infrastructure catalog. For more information on New Relic supported integrations, refer [Integrations](https://newrelic.com/instant-observability/).


### Limitations [#limitations]

* No support for sorting data in the Infrastructure catalog page.
13 changes: 7 additions & 6 deletions ...telligence/catalogs/repositoryCatalog.mdx → ...elligence/catalogs/repository-catalog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,18 +9,19 @@ freshnessValidatedDate: never
---


<Callout title="Preview">
We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
</Callout>


The <DNT>Repository catalog</DNT> is a tool designed to centralize and streamline the management of repositories within an organization. By providing a unified view of all repositories, it enhances cross-team collaboration and simplifies the discovery, access, and management of code repositories.

The <DNT>Repository catalog</DNT> is designed to break silos between teams and increase cross-team collaboration. It enables developers, Site Reliability Engineers (SREs), and other stakeholders to efficiently identify existing repositories, understand their purpose, and determine ownership or status. This centralized approach leads to improved collaboration, accountability, and productivity across the organization.


<Callout variant="important">

The Repository catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).

</Callout>


## Key features [#features]

- **Centralized Repository Discovery:** Quickly identify repositories relevant to services, projects, or <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, minimizing the time spent searching or consulting with colleagues.
Expand Down
Loading
Loading