From: Dominik Csapak <d.csapak@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager 3/3] ui: pve: nodes: add rrd time frame selector
Date: Fri, 6 Jun 2025 14:10:28 +0200 [thread overview]
Message-ID: <20250606121028.2595348-4-d.csapak@proxmox.com> (raw)
In-Reply-To: <20250606121028.2595348-1-d.csapak@proxmox.com>
so the user can select the timeframe and aggregation for the rrd graphs
also rename 'reload' to 'reload_rrd' and 'Msg::Reload' to
'Msg::ReloadRrd' so we're consistent with the qemu/lxc components.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
ui/src/pve/node.rs | 33 ++++++++++++++++++++++-----------
1 file changed, 22 insertions(+), 11 deletions(-)
diff --git a/ui/src/pve/node.rs b/ui/src/pve/node.rs
index b089f64..b3b002e 100644
--- a/ui/src/pve/node.rs
+++ b/ui/src/pve/node.rs
@@ -6,8 +6,7 @@ use yew::{
};
use proxmox_human_byte::HumanByte;
-use proxmox_rrd_api_types::{RrdMode, RrdTimeframe};
-use proxmox_yew_comp::{RRDGraph, Series};
+use proxmox_yew_comp::{RRDGraph, RRDTimeframe, RRDTimeframeSelector, Series};
use pwt::{
css::{AlignItems, ColorScheme, FlexFit},
prelude::*,
@@ -51,10 +50,11 @@ impl Into<VNode> for NodePanel {
}
pub enum Msg {
- Reload,
+ ReloadRrd,
ReloadStatus,
LoadFinished(Result<Vec<NodeDataPoint>, proxmox_client::Error>),
StatusLoadFinished(Result<NodeStatus, proxmox_client::Error>),
+ UpdateRrdTimeframe(RRDTimeframe),
}
pub struct NodePanelComp {
@@ -65,6 +65,8 @@ pub struct NodePanelComp {
mem_total_data: Rc<Series>,
status: Option<NodeStatus>,
+ rrd_time_frame: RRDTimeframe,
+
last_error: Option<proxmox_client::Error>,
last_status_error: Option<proxmox_client::Error>,
@@ -74,9 +76,9 @@ pub struct NodePanelComp {
}
impl NodePanelComp {
- async fn reload(remote: &str, node: &str) -> Msg {
+ async fn reload_rrd(remote: &str, node: &str, rrd_time_frame: RRDTimeframe) -> Msg {
let res = crate::pdm_client()
- .pve_node_rrddata(remote, node, RrdMode::Average, RrdTimeframe::Hour)
+ .pve_node_rrddata(remote, node, rrd_time_frame.mode, rrd_time_frame.timeframe)
.await;
Msg::LoadFinished(res)
@@ -93,7 +95,7 @@ impl yew::Component for NodePanelComp {
type Properties = NodePanel;
fn create(ctx: &yew::Context<Self>) -> Self {
- ctx.link().send_message(Msg::Reload);
+ ctx.link().send_message(Msg::ReloadRrd);
ctx.link().send_message(Msg::ReloadStatus);
Self {
time_data: Rc::new(Vec::new()),
@@ -101,6 +103,7 @@ impl yew::Component for NodePanelComp {
load_data: Rc::new(Series::new("", Vec::new())),
mem_data: Rc::new(Series::new("", Vec::new())),
mem_total_data: Rc::new(Series::new("", Vec::new())),
+ rrd_time_frame: RRDTimeframe::load(),
status: None,
last_error: None,
last_status_error: None,
@@ -112,13 +115,14 @@ impl yew::Component for NodePanelComp {
fn update(&mut self, ctx: &Context<Self>, msg: Self::Message) -> bool {
match msg {
- Msg::Reload => {
+ Msg::ReloadRrd => {
self._timeout = None;
let props = ctx.props();
let remote = props.remote.clone();
let node = props.node.clone();
+ let timeframe = self.rrd_time_frame;
self.async_pool.send_future(ctx.link().clone(), async move {
- Self::reload(&remote, &node).await
+ Self::reload_rrd(&remote, &node, timeframe).await
});
}
Msg::ReloadStatus => {
@@ -156,12 +160,11 @@ impl yew::Component for NodePanelComp {
let link = ctx.link().clone();
self._timeout = Some(gloo_timers::callback::Timeout::new(
ctx.props().rrd_interval,
- move || link.send_message(Msg::Reload),
+ move || link.send_message(Msg::ReloadRrd),
))
}
Err(err) => self.last_error = Some(err),
},
-
Msg::StatusLoadFinished(res) => {
match res {
Ok(status) => {
@@ -176,6 +179,11 @@ impl yew::Component for NodePanelComp {
move || link.send_message(Msg::ReloadStatus),
))
}
+ Msg::UpdateRrdTimeframe(rrd_time_frame) => {
+ self.rrd_time_frame = rrd_time_frame;
+ ctx.link().send_message(Msg::ReloadRrd);
+ return false;
+ }
}
true
}
@@ -194,7 +202,7 @@ impl yew::Component for NodePanelComp {
self.mem_total_data = Rc::new(Series::new("", Vec::new()));
self.async_pool = AsyncPool::new();
ctx.link()
- .send_message_batch(vec![Msg::Reload, Msg::ReloadStatus]);
+ .send_message_batch(vec![Msg::ReloadRrd, Msg::ReloadStatus]);
true
} else {
false
@@ -286,6 +294,9 @@ impl yew::Component for NodePanelComp {
Panel::new()
.class(FlexFit)
.title(title)
+ .with_tool(
+ RRDTimeframeSelector::new().on_change(ctx.link().callback(Msg::UpdateRrdTimeframe)),
+ )
.class(ColorScheme::Neutral)
.with_child(
// FIXME: add some 'visible' or 'active' property to the progress
--
2.39.5
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-06-06 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 12:10 [pdm-devel] [PATCH datacenter-manager 0/3] add rrd time frame selector for pve panels Dominik Csapak
2025-06-06 12:10 ` [pdm-devel] [PATCH datacenter-manager 1/3] ui: pve: qemu: add rrd time frame selector Dominik Csapak
2025-06-06 12:10 ` [pdm-devel] [PATCH datacenter-manager 2/3] ui: pve: lxc: " Dominik Csapak
2025-06-06 12:10 ` Dominik Csapak [this message]
2025-08-18 12:31 ` [pdm-devel] [PATCH datacenter-manager 0/3] add rrd time frame selector for pve panels Lukas Wagner
2025-08-19 8:10 ` Dominik Csapak
2025-08-19 12:36 ` [pdm-devel] applied: " Lukas Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250606121028.2595348-4-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox