bluerobotics / bluerobotics/BlueOS

core: frontend: improve monitoring and management of resource usage

Open
#3,009 0 comments 0 reactions 0 assignees View on GitHub
core enhancement triage ui
Dominant language
Vue
Stars
453
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
174

Description

### Current behaviour

Services, extensions, and the system as a whole have known resource limits / allocations and usage, but we don't always display them in a transparent manner, or allow easily acting on them via preferences or controls.

### Expected or desired behaviour

Building on #1482, #2328, #2572, #2820, etc, it would be nice to have a cohesive page and/or set of interface elements for
1. Displaying resource limits
2. Displaying resource usage
3. Configuring resource allocations
4. Providing reasonable resource-freeing action options
5. Configuring automatic usage threshold behaviour preferences
- Including notification options, both through BlueOS and MAVLink/Cockpit

For a given service/extension, it would be useful to have some kind of traffic light system (e.g. usage as expected, usage high, usage critical), combined with direct options to restart the service, clear logs, and/or clear data, and potentially include a preference for automatic old file deletion (file rotation) when particular limits are hit.

It would also be useful to show things in different views, e.g. the extensions page could have action icons/buttons corresponding to the existing usage bars, but a dedicated overview page could show comparative usage of each extension+service (and/or docker image/container) within a combined diagram per resource.

### Prerequisites

- [X] I have checked to make sure that a similar request has not already been filed or fixed.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing related issues #1482, #2328, #2572, and #2820, then inspect the extensions page and its existing usage bars. The issue needs a narrower entry point before implementation; done would require an agreed scope covering the selected monitoring, controls, and threshold preferences.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, frontend, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.