|
1 | 1 | --- |
2 | 2 | title: OpenShift Monitoring |
3 | | -description: Use Sysdig to monitor your running application |
| 3 | +description: Use OpenShift monitoring to monitor your running application |
4 | 4 | --- |
5 | 5 | <!--- cSpell:ignore appview ICPA openshiftconsole Theia userid toolset crwexposeservice gradlew bluemix ocinstall Mico crwopenlink crwopenapp swaggerui gitpat gituser buildconfig yourproject wireframe devenvsetup viewapp crwopenlink atemplatized rtifactoryurlsetup Kata Koda configmap Katacoda checksetup cndp katacoda checksetup Linespace igccli regcred REPLACEME Tavis pipelinerun openshiftcluster invokecloudshell cloudnative sampleapp bwoolf hotspots multicloud pipelinerun Sricharan taskrun Vadapalli Rossel REPLACEME cloudnativesampleapp artifactoryuntar untar Hotspot devtoolsservices Piyum Zonooz Farr Kamal Arora Laszewski Roadmap roadmap Istio Packt buildpacks automatable ksonnet jsonnet targetport podsiks SIGTERM SIGKILL minikube apiserver multitenant kubelet multizone Burstable checksetup handson stockbffnode codepatterns devenvsetup newwindow preconfigured cloudantcredentials apikey Indexyaml classname errorcondition tektonpipeline gradlew gitsecret viewapp cloudantgitpodscreen crwopenlink cdply crwopenapp --> |
6 | 6 |
|
7 | | -In IBM Garage Method, one of the Operate practices is to [automate application monitoring](https://www.ibm.com/garage/method/practices/manage/practice_automated_monitoring/). Sysdig automates application monitoring, enabling an operator to view stats and collect metrics about a Kubernetes cluster and its deployments. |
8 | | -The <Globals name="env" /> includes an IBM Cloud Monitoring with Sysdig service instance configured with a Sysdig agent installed in the environment's cluster. Simply by deploying your application into the <Globals name="env" />, Sysdig monitors it. |
| 7 | +In IBM Garage Method, one of the Operate practices is to [automate application monitoring](https://www.ibm.com/garage/method/practices/manage/practice_automated_monitoring/). OpenShift has embedded monitoring built in to help you view your application monitoring events, enabling an operator to view stats and collect metrics about a Kubernetes cluster and its deployments. |
9 | 8 |
|
10 | | -- Open the Sysdig web UI by navigating to the OpenShift web console and click on 9 squares icon. It gives a list of the developer tools. |
11 | | -- Select SysDig and navigate to SysDig UI. |
| 9 | +- Open the **Observe** console view by navigating to the **Developer View** in OpenShift web console and click on **Observe** menu. |
12 | 10 |
|
13 | | -## Sysdig Monitoring |
| 11 | +## Observing Apps in OpenShift |
14 | 12 |
|
15 | | -[IBM Cloud Monitoring with Sysdig](https://cloud.ibm.com/docs/services/Monitoring-with-Sysdig) explains how to configure and use an instance of the Sysdig service, but the <Globals name="env" /> has already done most of this for you. You can skip steps 1-3 about user access, provisioning an instance, and installing an agent. |
| 13 | +In the Observe view you are able to see the following views: |
| 14 | + - Dashboard, giving a summary view of the monitoring events for you namespace |
| 15 | + - Metrics , allows you to dig deeper into the various collected metrics for your namespace |
| 16 | + - Alerts, will allow you to see any generated alerts from your applications |
| 17 | + - Events, will allow you to see common events by kubernetes type |
16 | 18 |
|
17 | | -### Sysdig dashboard |
| 19 | +### Observe dashboard |
18 | 20 |
|
19 | | -Open the Sysdig web UI for your environment's cluster |
20 | | -- [Step 4: Launch the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started#getting-started-step5) explains how to open the web UI |
21 | | - - In the IBM Cloud dashboard, navigate to **Observability** > **Monitoring** |
22 | | - - Find the monitoring instance named after your environment's cluster, such as `showcase-dev-iks-sysdig` |
23 | | -  |
24 | | - - In the monitoring instance, press the **View Sysdig** button to open the Sysdig web UI |
| 21 | +Open the **Observe** Dashboard in the OpenShift console. |
| 22 | + - Make sure you have select the project you are working in `dev-{mjp}` |
| 23 | + - Change the Time Range to _Last 12 Hours_ you should see your microservice metrics being displayed |
| 24 | + - Scroll down the Dashboard and you will see other important information like CPU Quota , Memory Usage and Current Network usage |
| 25 | + - |
| 26 | + |
25 | 27 |
|
26 | | -### Explore your application |
| 28 | +### Explore metrics |
27 | 29 |
|
28 | | -By default, the Sysdig dashboard opens the **Explore** page on its **Deployments and Pods** grouping. |
| 30 | +You can drill into the detail behind the dashboard chats. You can look into the metrics for CPU, Memory and Network for the applications you have deployed in the namespace. |
29 | 31 |
|
30 | | -- Select your cluster |
| 32 | +- Click the drop-down to select CPU |
| 33 | +- Click the time drop-down to select 1h mins |
| 34 | +- Click Show PromSQL to show the underlying query being used to retrieve the data |
31 | 35 |
|
32 | | -By default, Sysdig opens its **Overview by Process** dashboard, which has panels showing stats about CPU, memory, and networking. |
33 | | -This is one of Sysdig's **Default Dashboards** (i.e. built-in dashboards). |
34 | | - |
35 | | -These are the cumulative totals for all of the pods running in the cluster. Hover over a graph and a key pops up to list |
36 | | -the pods and show each one's color. |
37 | | - |
38 | | -- Expand your cluster and namespace, then select your deployment |
39 | | - |
40 | | -This shows the stats for just the pods in your deployment. |
41 | | - |
42 | | -On the **Dashboard** page, you can create your own custom dashboards. |
43 | | - |
44 | | -[Step 5: Monitor your environment](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started#getting-started-step6) |
45 | | -of the Getting started tutorial gives some instructions on monitoring, managing, and what to do next. |
46 | | - |
47 | | - |
48 | | -## Give it a try |
49 | | - |
50 | | -Before you begin to monitor your application instances, make sure that you have [deployed an app](../deploy-app/) into your development cluster. This _Give it a Try_ uses [template-node-typescript](https://github.com/IBM/template-node-typescript) as an example. |
51 | | - |
52 | | -The **SysDig** service is already created, bound and configured to listen to monitoring metrics and events for your development cluster. You can see this in the HTTP overview. |
53 | | - |
54 | | -- Open the **SysDig** instance that is named the same as your development cluster. |
55 | | -- Go to **Dashboards** > **Default Dashboards** > **Applications** > **HTTP** |
56 | | - |
57 | | -The dashboard shows stats for all incoming HTTP requests for all apps in the cluster. Browse through these views to get a feel for what they're showing. |
58 | | - |
59 | | -### View your app's metrics |
60 | | - |
61 | | -Take a look at the metrics for your app. |
62 | | - |
63 | | -- Select the **Explore** page in the left nav menu |
64 | | -- On the Explore page, select the **Containerized Apps** grouping |
65 | | -- Search for your app, e.g. `hello-world-mjp` |
66 | | -- In the list of apps, select yours, e.g. `us.icr.io/mooc-team-one/hello-world-mjp:1.0.0-10` |
67 | | -- With your app selected, select **Hosts & Containers** > **Overview by Container** |
68 | | - |
69 | | - The Overview by Container dashboard shows metrics for the containers in your app. You will now see just the metrics for your app. You can view at different levels--from pod to namespace to node to cluster--giving you a fine grain access to your monitoring requirements. |
70 | | - |
71 | | -  |
| 36 | + |
72 | 37 |
|
73 | 38 | ## Conclusion |
74 | 39 |
|
75 | 40 | It's important to be able to monitor your deployed applications. |
76 | | -Here, the <Globals name="env" /> uses Sysdig Monitoring, but you never had to install or run Sysdig. |
77 | | -Just deploy your application into the <Globals name="env" /> and it gets monitored automatically. |
78 | | -After deploying your application, open the Sysdig web UI and browse the status, including the status |
| 41 | +Here, the OpenShift console includes an *Observe* view that helps you monitor your application metrics. |
| 42 | +Just deploy your application into your project namespace/project, and it gets monitored automatically. |
| 43 | +After deploying your application, open the *Observe* view from the OpenShift console and browse the status, including the status |
79 | 44 | of your cluster as a whole and your deployment in particular. |
80 | 45 |
|
81 | 46 | ### Learn more |
82 | 47 |
|
83 | | -Learn more about using SysDig Monitoring: |
| 48 | +Learn more about using [OpenShift Observe Monitoring](https://docs.openshift.com/container-platform/4.10/monitoring/monitoring-overview.html) click this link |
0 commit comments