You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/set-up-apache-skywalking-for-k8s-and-vm-monitoring-in-hpe-greenlake-private-cloud.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,7 +146,7 @@ As the first demo application, create a *SpingBoot* Web app that provides a R
146
146
147
147
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.
148
148
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.
### Monitor SpringBoot Application from SkyWalking UI
172
172
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:
174
174
175
175
```markdown
176
176
$ cat deployment.yaml
@@ -203,7 +203,7 @@ When the app gets deployed, the built-in Java agent will start collecting applic
203
203
204
204

205
205
206
-
Here is the application topology map:
206
+
Here is the *SpingBoot* Web app topology map:
207
207
208
208

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

215
215
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.
217
217
218
218
```markdown
219
219
├── app
@@ -271,18 +271,19 @@ deployment.apps/loadgen-deployment created
271
271
272
272
### Monitor Multi-tier Application from SkyWalking UI
273
273
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:
275
275
276
276

277
277
278
-
\- Multi-tier application topology:
278
+
Here is the multi-tier music application topology map:
279
279
280
280

281
281
282
-
\- Multi-tier application trace:
282
+
You can also check the multi-tier music application trace page:
0 commit comments