Skip to content

Commit 6505cb6

Browse files
adutta-newrelicadutta-newrelic
authored
Merge pull request #21908 from newrelic/Infrastructure-Catalog
Added prerequisite and improved doc
2 parents 9301ffe + e5b9b10 commit 6505cb6

File tree

60 files changed

+173
-4070
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

60 files changed

+173
-4070
lines changed

‎src/content/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx‎

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,170 @@
1+
---
2+
title: "Infrastructure catalog"
3+
tag:
4+
- "Service Architecture Intelligence"
5+
- "Infrastructure"
6+
- "Catalog"
7+
metaDescription: "Infrastructure catalog helps you manage your infrastructure resources in New Relic."
8+
freshnessValidatedDate: never
9+
---
10+
11+
<Callout variant="caution" title="Preview">
12+
We're still working on this feature, but we'd love for you to try it out!
13+
14+
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/).
15+
</Callout>
16+
17+
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.
18+
19+
Data is populated automatically from New Relic infrastructure agents and cloud integrations.
20+
21+
## Key features [#key-features]
22+
23+
* **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.
24+
25+
* **Application and service mapping:** See which applications and services are running on each compute resource to quickly assess impact and triage issues.
26+
27+
* **Clear ownership and accountability:** Easily identify owners for both infrastructure components and their dependent applications or services. This clarifies accountability when infrastructure issues arise.
28+
29+
* **Actionable resource insights:** Access insights into infrastructure activity—including health status, related incidents, scorecards, and more—to inform your resource optimization efforts.
30+
31+
* **Detailed resource configuration:** Quickly access current configuration data for each resource, enabling faster debugging and reducing context switching.
32+
33+
## Access the Infrastructure catalog [#access-infra-catalog]
34+
35+
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.
36+
37+
**Prerequisites:**
38+
39+
* 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).
40+
* (Recommended) Turn on [Autodiscovery](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/) to see how your applications connect to their underlying infrastructure resources. This helps you get more value from the Infrastructure catalog.
41+
42+
**To access the Infrastructure catalog inventory:**
43+
44+
1. Log in to your New Relic platform.
45+
2. Go to the left navigation pane > Catalogs > Infrastructure catalog.
46+
47+
<img
48+
title="Infra Catalog"
49+
alt="Infrastructure Catalog view with infrastructure entities, hosts, and services organized in a searchable interface"
50+
src="/images/infra-1.webp"
51+
/>
52+
53+
The Infrastructure Catalog page displays multiple columns to present various information for an infra resource:
54+
55+
<table>
56+
<thead>
57+
<tr>
58+
<th>UI</th>
59+
<th>Description</th>
60+
</tr>
61+
</thead>
62+
<tbody>
63+
<tr>
64+
<td>Name</td>
65+
<td>
66+
The name of the infrastructure entity.
67+
<ul>
68+
<li>Click entity name to open its Entity Overview page.</li>
69+
<li>Hover over the entity name to view additional details in a pop-up. You can also click links within this pop-up.</li>
70+
</ul>
71+
</td>
72+
</tr>
73+
<tr>
74+
<td>Type</td>
75+
<td>The type of the infrastructure resource. For example, `Host`, `KubernetesCluster`.</td>
76+
</tr>
77+
<tr>
78+
<td>Category</td>
79+
<td>
80+
A high-level grouping of resources. Supported categories include:
81+
<ul>
82+
<li>`AI + ML`</li>
83+
<li>`Analytics`</li>
84+
<li>`Compute`</li>
85+
<li>`Database`</li>
86+
<li>`Networking`</li>
87+
<li>`Other`</li>
88+
<li>`Queues/Streams/Events`</li>
89+
<li>`Security & Identity`</li>
90+
<li>`Storage`</li>
91+
</ul>
92+
</td>
93+
</tr>
94+
<tr>
95+
<td>Cloud</td>
96+
<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>
97+
</tr>
98+
<tr>
99+
<td>Score</td>
100+
<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 [Scorecards](https://docs.newrelic.com/docs/service-architecture-intelligence/scorecards/getting-started/).</td>
101+
</tr>
102+
<tr>
103+
<td>Team</td>
104+
<td>
105+
The team responsible for the entity.
106+
<ul>
107+
<li>Click a team name to navigate to that team's page.</li>
108+
<li>Hover over a team name to view additional details.</li>
109+
<li>If a team is not assigned, click Assign Team and select the responsible team.</li>
110+
</ul>
111+
For more information, refer [Teams](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/teams/).
112+
</td>
113+
</tr>
114+
<tr>
115+
<td>Services</td>
116+
<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>
117+
</tr>
118+
<tr>
119+
<td>Alerts</td>
120+
<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 [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>
121+
</tr>
122+
<tr>
123+
<td>Region</td>
124+
<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.
125+
The following tags are checked in order:
126+
<ul>
127+
<li>`region`</li>
128+
<li>`cloud.region`</li>
129+
<li>`aws.awsRegion`</li>
130+
<li>`azure.regionName`</li>
131+
<li>`gcp.region`</li>
132+
</ul>
133+
</td>
134+
</tr>
135+
<tr>
136+
<td>Availability Zone</td>
137+
<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.
138+
The following tags are checked in order:
139+
<ul>
140+
<li>`availabilityZone`</li>
141+
<li>`cloud.availability_Zone`</li>
142+
<li>`aws.availabilityZone`</li>
143+
<li>`awsAvailabilityZone`</li>
144+
<li>`azure.availabilityZone`</li>
145+
<li>`gcp.zone`</li>
146+
</ul>
147+
</td>
148+
</tr>
149+
<tr>
150+
<td>Environment</td>
151+
<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.
152+
The following tags are checked in order:
153+
<ul>
154+
<li>`Environment`</li>
155+
<li>`environment`</li>
156+
<li>`env`</li>
157+
</ul>
158+
</td>
159+
</tr>
160+
</tbody>
161+
</table>
162+
163+
### Add new data [#add-new-data]
164+
165+
To add additional data to your Infrastructure catalog click **+ 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/).
166+
167+
168+
### Limitations [#limitations]
169+
170+
No support for sorting data in the Infrastructure catalog page.

‎src/content/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx‎ renamed to ‎src/content/docs/service-architecture-intelligence/catalogs/repository-catalog.mdx‎

File renamed without changes.

‎src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-10-2025.mdx‎

Lines changed: 0 additions & 61 deletions
This file was deleted.

0 commit comments

Comments
 (0)