Upstream software project

sysusage

Apache configuration for sysusage

About sysusage

Apache configuration for sysusage

This project links 8 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 4 package records; Fedora 44: 4 package records. Catalog coverage diagram, not an application screenshot.sysusage: recorded package coverageFedora 434 recordsFedora 444 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sysusage
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44
License expression
GPL-3.0-or-later
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

SysUsage continuously monitor your systems information and generate periodic graphical reports using rrdtool or JavaScript jqplot library. All reports are shown through a web interface. SysUsage grabs all system activities using Sar and system commands allowing you to keep tracks of your computer or server activity during its life. It is a great help for performance analysis and resources management. The threshold notification can alarm you when the system capabilities are reached by sending SMTP messages or through Nagios reports. By default it will monitor all you need to know on your server activity, it is written in Perl and should works on all Unix like platforms. It doesn't require a Database system like MySQL or PostgreSQL but relies on rrdtool. In addition you can embedded your own plugins written in any programming language. Since release 5.0 SysUsage can be run from a centralized place where collected statistics will be stored and where graphics will be rendered. Unlike other monitoring tools with lot of administration work, SysUsage is design to have the least possible things to configure and a high level of admin system knowledge. Each server can also be self monitored and you just have to connect your browser to the web interface to know its health level. SysUsage is design with simplicity in mind. providing all relevant statistics from the servers within an intuitive web interface and without spending too much time to configure it, if you know Nagios, you know what I mean. You will especially like SysUsage for that.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package sysusage

    43 (Fedora 43) (Unspecified): System monitoring based on Perl, rrdtool, and sysstat

    5.7-24.fc43: noarch

    Source: sysusage

  2. Package sysusage-common

    43 (Fedora 43) (Unspecified): Common files for sysusage

    5.7-24.fc43: noarch

    Source: sysusage

  3. Package sysusage-httpd

    43 (Fedora 43) (Unspecified): Apache configuration for sysusage

    5.7-24.fc43: noarch

    Source: sysusage

  4. Package sysusage-rsysusage

    43 (Fedora 43) (Unspecified): Remote utility for sysusage

    5.7-24.fc43: noarch

    Source: sysusage

Fedora 44

  1. Package sysusage

    44 (Fedora 44) (Unspecified): System monitoring based on Perl, rrdtool, and sysstat

    5.7-25.fc44: noarch

    Source: sysusage

  2. Package sysusage-common

    44 (Fedora 44) (Unspecified): Common files for sysusage

    5.7-25.fc44: noarch

    Source: sysusage

  3. Package sysusage-httpd

    44 (Fedora 44) (Unspecified): Apache configuration for sysusage

    5.7-25.fc44: noarch

    Source: sysusage

  4. Package sysusage-rsysusage

    44 (Fedora 44) (Unspecified): Remote utility for sysusage

    5.7-25.fc44: noarch

    Source: sysusage

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.