Skip to content

Commit 7a86425

Browse files
committed
update image alt text syntax
1 parent e541a29 commit 7a86425

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

architecture.html.md.erb

+7-7
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ This section includes the following diagrams:
3232
### <a id='firehose-architecture'></a> Loggregator Firehose architecture
3333
<a id='loggregator-architecture'></a>
3434

35-
The following diagram shows how logs and metrics are transported from components and apps on your deployment to Loggregator Firehose consumers, such as nozzles, monitoring tools, or third party software.
35+
The following diagram shows how logs and metrics are transported from components and apps on your deployment to Loggregator Firehose consumers, such as nozzles, monitoring tools, or third-party software.
3636

37-
![alt-text="How logs and metrics are transported. "](./images/architecture/firehose-reference.png)
37+
![How logs and metrics are transported.](./images/architecture/firehose-reference.png)
3838

3939
[View a larger version of this image.](images/architecture/firehose-reference.png)
4040

@@ -68,7 +68,7 @@ Similar to the Loggregator Firehose Architecture, the shared-nothing architectur
6868

6969
In contrast to the Loggregator Firehose architecture, logs and metrics pass through fewer components in the shared-nothing architecture.
7070

71-
![alt-text="In shared-nothing architecture, the logs and metrics egress directly from deployment VMs, eliminating the need for VMs running doppler and traffic controller components."](./images/architecture/shared-nothing-reference.png)
71+
![In shared-nothing architecture, the logs and metrics egress directly from deployment VMs, eliminating the need for VMs running doppler and traffic controller components.](./images/architecture/shared-nothing-reference.png)
7272

7373
[View a larger version of this image.](images/architecture/shared-nothing-reference.png)
7474

@@ -98,7 +98,7 @@ The following components are included in the shared-nothing architecture, as sho
9898

9999
The following diagram shows the architecture of a deployment that uses System Metrics Agents to collect VM and system-level metrics.
100100

101-
![alt-text="NSX-T Overview"](./images/architecture/system-metrics-agents.png)
101+
![NSX-T Overview](./images/architecture/system-metrics-agents.png)
102102

103103
[View a larger version of this image.](./images/architecture/system-metrics-agents.png)
104104

@@ -138,7 +138,7 @@ The following describes the transport of logs and metrics from VMs through syste
138138

139139
The following diagram shows the transport of logs and metrics from VMs on your deployment:
140140

141-
![alt-text="Transport of logs and metrics from VMs on your deployment"](./images/architecture/vms.png)
141+
![Transport of logs and metrics from VMs on your deployment.](./images/architecture/vms.png)
142142

143143
### <a id='firehose'></a> How Loggregator Firehose forwards logs and metrics
144144

@@ -157,7 +157,7 @@ The following information describes how the Loggregator Firehose sends logs and
157157

158158
The following diagram shows the flow of logs and metrics through the Loggregator Firehose as previously described:
159159

160-
![alt-text="A Loggregator Agent appears inside a square labeled VMs. Loggregator Agents send to Dopplers, located on Doppler VMs. Dopplers, in turn, send to both Traffic Controllers and Reverse Log Proxies."](./images/architecture/firehose.png)
160+
![A Loggregator Agent appears inside the VMs block. Loggregator Agents send to Dopplers, located on Doppler VMs. Dopplers, in turn, send to both Traffic Controllers and Reverse Log Proxies.](./images/architecture/firehose.png)
161161

162162
### <a id='consumers'></a> How consumers receive logs and metrics
163163

@@ -173,7 +173,7 @@ Integrations with observability or monitoring products receive logs and metrics
173173

174174
The following diagram shows how consumers of logs and metrics receive logs and metrics from your deployment:
175175

176-
![alt-text="A Forwarder Agent appears inside a square labeled VMs. Apps are shown sending to the Forwarder Agent, and Components are shown sending metrics to the the Forwarder Agent. Components also send logs to syslog."](./images/architecture/consumers.png)
176+
![A Forwarder Agent is one of the VMs in the VMs block. Apps are shown sending to the Forwarder Agent, and Components are shown sending metrics to the the Forwarder Agent. Components also send logs to syslog.](./images/architecture/consumers.png)
177177

178178
## <a id='bosh-metrics'></a> Related BOSH components
179179

0 commit comments

Comments
 (0)