Monitor and control applications
Let’s learn how to monitor and control applications on SPEKTRA Edge.
What you need
To go through this page, you need the followings.
- an access to the SPEKTRA Edge dashboard
- an active project
- a device provisioned under the project
- an application running on the device
With these, let’s dive in managing applications on SPEKTRA Edge.
Note
The getting started guide will help you to set those requirements up. Please go through the guide in case if you miss some of those.Application overview
Application overview page is the main dashboard to manage applications on SPEKTRA Edge.
To get there from the Project overview page, click the Manage pods button located in the Pods section of the Project overview page.
Manage pods button in the Pods section of the Project overview page.
Click the name of the application you want to manage, counter in this example, to get to the Application overview page of the application.
Clicking the application name to go to the Application overview page.
Here on the Application overview page, you can do the majority of the taskes to manage applications, such as:
- observing the application’s status
- checking the application’s Docker compose file content
- monitoring the application’s resource usages, such as CPU and memory
- examining the application’s logs
- controling your application
It also offers the cuttle port forward command, which you can copy and run on your local machine to access your application through the SPEKTRA Edge port forwarding capability.
Copy port forward command option in the Application overview page.
Application statuses
Here is the list of application statuses monitored on SPEKTRA Edge.
| Status | Description |
|---|---|
| Pending | The application is accepted by the system and it’s under processing to be launched. It’s the PENDING state of the Pod.Status.Phase enumeration type. |
| Running | The application is running, which is that its all containers supposed to be running are up and running. It’s the RUNNING state of the Pod.Status.Phase enumeration type. |
| Succeeded | The application is terminated with the success exit code. It’s the SUCCEEDED state of the Pod.Status.Phase enumeration type. |
| Failed | The application encountered an issue and some or all of the containers are not running. This phase happens after the containers are initially created successfully. It’s the FAILED state of the Pod.Status.Phase enumeration type. |
| Offline | The application does not respond anymore. This phase happens after the containers were initially created successfully. It’s the UNKNOWN state of the Pod.Status.Phase enumeration type. |
| Image download failed | The application failed to download the container image. It’s the IMAGE_DOWNLOAD_FAILED state of the Pod.Status.Phase enumeration type. |
| Initialization failed | The application failed to initialize or the validation of the application definition had some errors, typically caused by the Docker compose file syntax errors or the system errors on devices such as disk full. It’s the INIT_FAILED state of the Pod.Status.Phase enumeration type. |
| Pod create failed | The application failed for the creation due to either by the docker runtime error or the keyword errors. It’s the POD_CREATE_FAILED state of the Pod.Status.Phase enumeration type. |
Container states
Here is the list of Container’s state, which is the composition of the application status explained above. The Containers section of the Application overview page shows the container states.
| State | Description |
|---|---|
| Waiting | The container is waiting to start. It’s the WAITING state of the Pod.Status.Container.State enumeration type. |
| Running | The container is running. It’s the RUNNING state of the Pod.Status.Container.State enumeration type. |
| Terminated | The container is terminated. It’s the TERMINATED state of the Pod.Status.Container.State enumeration type. |
Application metrics
You can monitor the container’s resource usage on the dashboard.
Go to the Containers usage section of the Application overview page and select the type of resource you want to monitor. Click the right side of the time range section to specify the duration of the time-series to be shown on the graph.
Specifying the duration of the time to show the application CPU usage.
Application logs
You can retrieve each container’s logs on the dashboard.
Specify the name of the container you want to show the logs by clicking the pull down menu of the Logs section on the Application overview page.
Click Start to retrieve the live logs of the container.
You can also download the logs by clicking the Download icon on the Logs menu bar.
Observing the redis container’s logs.
Control applications
You can control applications from the dashboard.
Here is the list of operations you can perform:
- delete
- restart
Click the the vertical three-dots right next to the application’s name in the Application overview page to show the pull-down menu and select the operation you want to perform.
Restarting the application by clicking the Restart option of the pull-down menu on the Application overview page.
Next step
Congratulations!
With the understanding of the application management on SPEKTRA Edge, we hope you gained the fundamental concept of the application life cycle happens on the SPEKTRA Edge platform.
Please go ahaed next to the device management section as part of the SPEKTRA Edge mastery.