Bug 362463 - Add file monitor to ksysguard
Summary: Add file monitor to ksysguard
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.6.3
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-29 08:48 UTC by adr.fantini
Modified: 2024-09-23 21:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adr.fantini 2016-04-29 08:48:19 UTC
Ksysguard finds by itself most sensors on each machine, but some may be missed, not included or manually generated by the user.

It'd be nice if ksysguard added the ability to manually choose a file to monitor, either by reading a number to display in one of the standard plots (e.g. line graphs) or by just displaying the content of the file.

For example, if at all times I want to plot the current that goes through my battery, I'd like to show the content of the file:
/sys/class/power_supply/BAT0/current_now

Maybe even having the ability to multiply by a constant would be nice (e.g. current is usually given in microAmperes).

Another case is that in which I want to monitor a taxt file generated by e.g. a daemon, and I'd like ksysguard to show it in a tab side by side with e.g. disk I/O. In this case this is a simple file monitor implementation.

Reproducible: Always
Comment 1 Richard Llom 2019-03-15 14:24:08 UTC
Confirmed.

Note that ksysguard has an lmsensors interface, so via this interface it is already possible to track a lot of hardware sensors.

(In theory at leat, because power sensors are currently not supported in ksysguard, see bug 302667)
Comment 2 Christoph Cullmann 2024-09-23 21:01:27 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!