@cryptotaxi247 / netdata-1 / commits / 494b2061c

web/gui: add systemdunits info to the dashboard_info.js (#10904)

Co-authored-by: Vladimir Kobal <vlad@prokk.net>

Ilya Mashchenko committed Apr 14, 2021 at 13:23 UTC 494b2061c070133096ace9c60ba8a649248068a5
1 file changed +73
web/gui/dashboard_info.js
+73
@@ -595,6 +595,18 @@ netdataDashboard.menu = {
595 info: 'Detailed statistics for each group of processes controlled by <b><a href="http://supervisord.org/">Supervisor</a></b>. ' +
596 'Netdata collects these metrics using <a href="http://supervisord.org/api.html#supervisor.rpcinterface.SupervisorNamespaceRPCInterface.getAllProcessInfo" target="_blank"><code>getAllProcessInfo</code></a> method.'
597 },
598 +
599 + 'systemdunits': {
600 + title: 'systemd units',
601 + icon: '<i class="fas fa-cogs"></i>',
602 + info: '<b>systemd</b> provides a dependency system between various entities called "units" of 11 different types. ' +
603 + 'Units encapsulate various objects that are relevant for system boot-up and maintenance. ' +
604 + 'Units may be <code>active</code> (meaning started, bound, plugged in, depending on the unit type), ' +
605 + 'or <code>inactive</code> (meaning stopped, unbound, unplugged), ' +
606 + 'as well as in the process of being activated or deactivated, i.e. between the two states (these states are called <code>activating</code>, <code>deactivating</code>). ' +
607 + 'A special <code>failed</code> state is available as well, which is very similar to <code>inactive</code> and is entered when the service failed in some way (process returned error code on exit, or crashed, an operation timed out, or after too many restarts). ' +
608 + 'For detailes, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.html" target="_blank"> systemd(1)</a>.'
609 + },
610 };
611
612
@@ -3863,4 +3875,65 @@ netdataDashboard.context = {
3875 '<code>0</code> - stopped, <code>10</code> - starting, <code>20</code> - running, <code>30</code> - backoff,' +
3876 '<code>40</code> - stopping, <code>100</code> - exited, <code>200</code> - fatal, <code>1000</code> - unknown.'
3877 },
3878 +
3879 + // ------------------------------------------------------------------------
3880 + // Systemd units
3881 +
3882 + 'systemd.service_units_state': {
3883 + info: 'Service units start and control daemons and the processes they consist of. ' +
3884 + 'For details, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.service.html#" target="_blank"> systemd.service(5)</a>'
3885 + },
3886 +
3887 + 'systemd.socket_unit_state': {
3888 + info: 'Socket units encapsulate local IPC or network sockets in the system, useful for socket-based activation. ' +
3889 + 'For details about socket units, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.socket.html#" target="_blank"> systemd.socket(5)</a>, ' +
3890 + 'for details on socket-based activation and other forms of activation, see <a href="https://www.freedesktop.org/software/systemd/man/daemon.html#" target="_blank"> daemon(7)</a>.'
3891 + },
3892 +
3893 + 'systemd.target_unit_state': {
3894 + info: 'Target units are useful to group units, or provide well-known synchronization points during boot-up, ' +
3895 + 'see <a href="https://www.freedesktop.org/software/systemd/man/systemd.target.html#" target="_blank"> systemd.target(5)</a>.'
3896 + },
3897 +
3898 + 'systemd.path_unit_state': {
3899 + info: 'Path units may be used to activate other services when file system objects change or are modified. ' +
3900 + 'See <a href="https://www.freedesktop.org/software/systemd/man/systemd.path.html#" target="_blank"> systemd.path(5)</a>.'
3901 + },
3902 +
3903 + 'systemd.device_unit_state': {
3904 + info: 'Device units expose kernel devices in systemd and may be used to implement device-based activation. ' +
3905 + 'For details, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.device.html#" target="_blank"> systemd.device(5)</a>.'
3906 + },
3907 +
3908 + 'systemd.mount_unit_state': {
3909 + info: 'Mount units control mount points in the file system. ' +
3910 + 'For details, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.mount.html#" target="_blank"> systemd.mount(5)</a>.'
3911 + },
3912 +
3913 + 'systemd.automount_unit_state': {
3914 + info: 'Automount units provide automount capabilities, for on-demand mounting of file systems as well as parallelized boot-up. ' +
3915 + 'See <a href="https://www.freedesktop.org/software/systemd/man/systemd.automount.html#" target="_blank"> systemd.automount(5)</a>.'
3916 + },
3917 +
3918 + 'systemd.swap_unit_state': {
3919 + info: 'Swap units are very similar to mount units and encapsulate memory swap partitions or files of the operating system. ' +
3920 + 'They are described in <a href="https://www.freedesktop.org/software/systemd/man/systemd.swap.html#" target="_blank"> systemd.swap(5)</a>.'
3921 + },
3922 +
3923 + 'systemd.timer_unit_state': {
3924 + info: 'Timer units are useful for triggering activation of other units based on timers. ' +
3925 + 'You may find details in <a href="https://www.freedesktop.org/software/systemd/man/systemd.timer.html#" target="_blank"> systemd.timer(5)</a>.'
3926 + },
3927 +
3928 + 'systemd.scope_unit_state': {
3929 + info: 'Slice units may be used to group units which manage system processes (such as service and scope units) ' +
3930 + 'in a hierarchical tree for resource management purposes. ' +
3931 + 'See <a href="https://www.freedesktop.org/software/systemd/man/systemd.scope.html#" target="_blank"> systemd.scope(5)</a>.'
3932 + },
3933 +
3934 + 'systemd.slice_unit_state': {
3935 + info: 'Scope units are similar to service units, but manage foreign processes instead of starting them as well. ' +
3936 + 'See <a href="https://www.freedesktop.org/software/systemd/man/systemd.slice.html#" target="_blank"> systemd.slice(5)</a>.'
3937 + },
3938 +
3939 };