Skip to content

Commit 16ef474

Browse files
committed
Update Blog “set-up-apache-skywalking-for-k8s-and-vm-monitoring-in-hpe-greenlake-private-cloud”
1 parent dd62203 commit 16ef474

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

content/blog/set-up-apache-skywalking-for-k8s-and-vm-monitoring-in-hpe-greenlake-private-cloud.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ As the first demo application, create a *SpingBoot* Web app that provides a R
146146

147147
By building a *Docker* image using the generated *jar* file, this *SpringBoot* app can be easily deployed as a containerized application to the Kubernetes cluster.
148148

149-
Apache SkyWalking provides a list of agents per programming language that can be used for building into corresponding aservice which collects application data and exports them to the SkyWalking OAP server.
149+
Apache SkyWalking provides a list of agents per programming language that can be used for building into corresponding service which collects application data and exports them to the SkyWalking OAP server.
150150

151151
![](/img/sw-agents.png)
152152

@@ -170,7 +170,7 @@ ENTRYPOINT ["java","-javaagent:/opt/agent/skywalking-agent.jar=agent.namespace=d
170170

171171
### Monitor SpringBoot Application from SkyWalking UI
172172

173-
After build the Docker image *guopingjia/springboot-k8s-demo:pce* and push it to the *DockerHub*, we deploy the *SpringBoot* app to the Kubernetes cluster:
173+
After build the Docker image *guopingjia/springboot-k8s-demo:pce* and push it to the *DockerHub* registry, we deploy the *SpringBoot* app to the Kubernetes cluster:
174174

175175
```markdown
176176
$ cat deployment.yaml
@@ -203,7 +203,7 @@ When the app gets deployed, the built-in Java agent will start collecting applic
203203

204204
![](/img/java-app.png)
205205

206-
Here is the application topology map:
206+
Here is the *SpingBoot* Web app topology map:
207207

208208
![](/img/java-app-map.png)
209209

@@ -213,7 +213,7 @@ As the second demo application, we will deploy a multi-tier *music* applicati
213213

214214
![](/img/multl-tier-app-music.png)
215215

216-
In order to monitor the multi-tier application from Apache SkyWalking, we need to pickup the SkyWalking agent per programming language and rebuild corresponding service to instrument the applicaiton to the SkyWalking OAP server.
216+
In order to monitor the multi-tier application from Apache SkyWalking, we need to pickup the SkyWalking agent per programming language and rebuild corresponding service to instrument the application to the SkyWalking OAP server.
217217

218218
```markdown
219219
├── app
@@ -271,18 +271,19 @@ deployment.apps/loadgen-deployment created
271271

272272
### Monitor Multi-tier Application from SkyWalking UI
273273

274-
\- Multi-tier application services:
274+
When the multi-tier app gets deployed, the agents built with each microservice will start collecting application data and post it to the SkyWalking OAP. The multi-tier music application metrics will be available in the SkyWalking UI, under _General Service_ tab:
275275

276276
![](/img/multl-tier-app.png)
277277

278-
\- Multi-tier application topology:
278+
Here is the multi-tier music application topology map:
279279

280280
![](/img/multl-tier-app-map.png)
281281

282-
\- Multi-tier application trace:
282+
You can also check the multi-tier music application trace page:
283283

284284
![](/img/sw-app-trace.png)
285285

286+
286287
\- Multi-tier application alarms:
287288

288289
![](/img/sw-app-alarms.png)

0 commit comments

Comments
 (0)