Skip to content

Commit 0928386

Browse files
committed
removed expanded references from image names
1 parent 16b9df3 commit 0928386

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/operator-5g-core/concept-observability-analytics.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Observability has three pillars: metrics, tracing, and logs. Azure Operator 5G C
1919
The following components provide observability for Azure Operator 5G Core:
2020

2121

22-
[:::image type="content" source="media/concept-observability-analytics/observability-overview.png" alt-text="Diagram of text boxes showing the components that support observability functions for Azure Operator 5G Core.":::](media/concept-observability-analytics/observability-overview-expanded.png#lightbox)
22+
[:::image type="content" source="media/concept-observability-analytics/observability-overview.png" alt-text="Diagram of text boxes showing the components that support observability functions for Azure Operator 5G Core.":::](media/concept-observability-analytics/observability-overview.png#lightbox)
2323

2424
### Observability open source components
2525

@@ -37,7 +37,7 @@ Elasticsearch, Fluentd, and Kibana (EFK) provide a distributed logging system us
3737
### Architecture
3838
The following diagram shows EFK architecture:
3939

40-
[:::image type="content" source="media/concept-observability-analytics/elasticsearch-fluentd-kibana-architecture.png" alt-text="Diagram of text boxes showing the Elasticsearch, Fluentd, and Kibana (EFK) distributed logging system used to troubleshoot microservices in Azure Operator 5G Core.":::](media/concept-observability-analytics/elasticsearch-fluentd-kibana-architecture-expanded.png#lightbox)
40+
[:::image type="content" source="media/concept-observability-analytics/elasticsearch-fluentd-kibana-architecture.png" alt-text="Diagram of text boxes showing the Elasticsearch, Fluentd, and Kibana (EFK) distributed logging system used to troubleshoot microservices in Azure Operator 5G Core.":::](media/concept-observability-analytics/elasticsearch-fluentd-kibana-architecture.png#lightbox)
4141

4242
> [!NOTE]
4343
> Sections of the following linked content is available only to customers with a current Affirmed Networks support agreement. To access the content, you must have Affirmed Networks login credentials. If you need assistance, please speak to the Affirmed Networks Support Team.
@@ -123,7 +123,7 @@ Grafana provides dashboards to visualize the collected data.
123123

124124
The following diagram shows how the different components of the metrics framework interact with each other.
125125

126-
[:::image type="content" source="media/concept-observability-analytics/network-functions.png" alt-text="Diagram of text boxes showing interaction between metrics frameworks components in Azure Operator 5G Core.":::](media/concept-observability-analytics/network-functions-expanded.png#lightbox)
126+
[:::image type="content" source="media/concept-observability-analytics/network-functions.png" alt-text="Diagram of text boxes showing interaction between metrics frameworks components in Azure Operator 5G Core.":::](media/concept-observability-analytics/network-functions.png#lightbox)
127127

128128
The core components of the metrics framework are:
129129

@@ -199,7 +199,7 @@ IstioHTTPRequestLatencyTooHigh: Requests are taking more than the <configured
199199

200200
Azure Operator 5G Core uses the OpenTelemetry Protocol (OTLP) in Jaeger tracing. OTLP replaces the Jaeger agent in fed-paas-helpers. Azure Operator 5G Core deploys the fed-otel_collector federation. The OpenTelemetry (OTEL) Collector runs as part of the fed-otel_collector namespace:
201201

202-
[:::image type="content" source="media/concept-observability-analytics/jaeger-components.png" alt-text="Diagram of text boxes showing Jaeger tracing and OpenTelemetry Protocol components in Azure Operator 5G Core.":::](media/concept-observability-analytics/jaeger-components-expanded.png#lightbox)
202+
[:::image type="content" source="media/concept-observability-analytics/jaeger-components.png" alt-text="Diagram of text boxes showing Jaeger tracing and OpenTelemetry Protocol components in Azure Operator 5G Core.":::](media/concept-observability-analytics/jaeger-components.png#lightbox)
203203

204204
Jaeger tracing uses the following workflow:
205205

articles/operator-5g-core/overview-product.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 04/12/2024
1414

1515
Azure Operator 5G Core Preview is a carrier-grade, Any-G, hybrid mobile packet core with fully integrated network functions that run both on-premises and in-cloud. Service providers can deploy resilient networks with high performance and at high capacity while maintaining low latency. Azure Operator 5G Core is ideal for Tier 1 consumer networks, mobile network operators (MNO), virtual network operators (MVNOs), enterprises, IoT, fixed wireless access (FWA), and satellite network operators (SNOs).
1616

17-
[:::image type="content" source="media/overview-product/architecture-5g-core.png" alt-text="Diagram of text boxes showing the components that comprise Azure Operator 5G Core.":::](media/overview-product/architecture-5g-core-expanded.png#lightbox)
17+
[:::image type="content" source="media/overview-product/architecture-5g-core.png" alt-text="Diagram of text boxes showing the components that comprise Azure Operator 5G Core.":::](media/overview-product/architecture-5g-core.png#lightbox)
1818

1919
The power of Azure's global footprint ensures global coverage and operating infrastructure at scale, coupled with Microsoft's Zero Trust security framework to provide secure and reliable connectivity to cloud applications. 
2020

@@ -68,7 +68,7 @@ Azure Operator 5G Core offers the following network functions: 
6868

6969
Any-G is built on top of Azure Operator Nexus and Azure – with flexible Network Function (NF) placement based on the operator use case. Different use cases drive NF deployment topologies. Network Functions can be placed geographically closer to the users for scenarios such as consumer, low latency, and MEC or centralized for machine to machine (Internet of Things) and enterprise scenarios. Deployment is API driven regardless of the placement of the network functions.
7070

71-
[:::image type="content" source="media/overview-product/deployment-models.png" alt-text="Diagram describing supported deployment models for Azure Operator 5G Core.":::](media/overview-product/deployment-models-expanded.png#lightbox)
71+
[:::image type="content" source="media/overview-product/deployment-models.png" alt-text="Diagram describing supported deployment models for Azure Operator 5G Core.":::](media/overview-product/deployment-models.png#lightbox)
7272

7373

7474
### Resiliency 

0 commit comments

Comments
 (0)