forked from patternfly/patternfly-quickstarts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmonitor-sampleapp-quickstart.tsx
More file actions
78 lines (76 loc) · 3.87 KB
/
monitor-sampleapp-quickstart.tsx
File metadata and controls
78 lines (76 loc) · 3.87 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
import { QuickStart } from '@patternfly/quickstarts';
import GithubIcon from '@patternfly/react-icons/dist/js/icons/github-icon';
export const monitorSampleAppQuickStart: QuickStart = {
apiVersion: 'console.openshift.io/v1',
kind: 'QuickStarts',
metadata: {
name: 'monitor-sampleapp',
},
spec: {
version: 4.7,
displayName: 'Monitoring your sample application',
durationMinutes: 10,
icon: <GithubIcon />,
description: `Now that you’ve created a sample application and added health checks, let’s monitor your application.`,
prerequisites: [`You completed the "Getting started with a sample" quick start.`],
introduction: `### This quick start shows you how to monitor your sample application.
You should have previously created the **sample-app** application and **nodejs-sample** deployment via the **Get started with a sample** quick start. If you haven't, you may be able to follow these tasks with any existing deployment.`,
tasks: [
{
title: `Viewing the monitoring details of your sample application`,
description: `### To view the details of your sample application:
1. Go to the project your sample application was created in.
2. In the **</> Developer** perspective, go to **Topology** view.
3. Click on the **nodejs-sample** deployment to view its details.
4. Click on the **Monitoring** tab in the side panel.
You can see context sensitive metrics and alerts in the **Monitoring** tab.`,
review: {
instructions: `#### To verify you can view the monitoring information:
1. Do you see a **Metrics** accordion in the side panel?
2. Do you see a **View monitoring dashboard** link in the **Metrics** accordion?
3. Do you see three charts in the **Metrics** accordion: **CPU Usage**, **Memory Usage** and **Receive Bandwidth**?`,
failedTaskHelp: `This task isn’t verified yet. Try the task again.`,
},
summary: {
success: `You have learned how you can monitor your sample app!`,
failed: `Try the steps again.`,
},
},
{
title: `Viewing your project monitoring dashboard`,
description: `### To view the project monitoring dashboard in the context of **nodejs-sample**:
1. Click on the **View monitoring dashboard** link in the side panel.
2. You can change the **Time Range** and **Refresh Interval** of the dashboard.
3. You can change the context of the dashboard as well by clicking on the drop-down list. Select a specific workload or **All Workloads** to view the dashboard in the context of the entire project.`,
review: {
instructions: `#### To verify that you are able to view the monitoring dashboard:
Do you see metrics charts in the dashboard?`,
failedTaskHelp: `This task isn’t verified yet. Try the task again.`,
},
summary: {
success: `You have learned how to view the dashboard in the context of your sample app!`,
failed: `Try the steps again.`,
},
},
{
title: `Viewing custom metrics`,
description: `### To view custom metrics:
1. Click on the **Metrics** tab of the **Monitoring** page.
2. Click the **Select Query** drop-down list to see the available queries.
3. Click on **Filesystem Usage** from the list to run the query.`,
review: {
instructions: `#### Verify you can see the chart associated with the query:
Do you see a chart displayed with filesystem usage for your project? Note: select **Custom Query** from the dropdown to create and run a custom query utilizing PromQL.
`,
failedTaskHelp: `This task isn’t verified yet. Try the task again.`,
},
summary: {
success: `You have learned how to run a query!`,
failed: `Try the steps again.`,
},
},
],
conclusion: `You have learned how to access workload monitoring and metrics!`,
nextQuickStart: [``],
},
};