# defined by a name, an icon and a serie of lines described as follow: # Status page is split in strips displaying information. # name of the page displayed into the drop down menu in # It is possible to define multiple pages. This code can use status information with # the keyword 'data' including the 'data.hostname' available natively # javascript code defining the text displayed into # the icon to be displayed into RPi-Monitor title bar # is the link to another RPi-Monitor running # is the name printed into the drop down menu # friend is identified by its and is described by the 2 following # top left menu visible if at least one friends is configured. # Friends are defining a displayed name and a link reachable from a # You can refer to swap data extraction to see an example. # Note: Static values are accessible for the post processing using the # they reach their limit (Ex: network graphs) # These limits are usefull to handle counter that fall down to 0 when # value, it will be stored int RRD database as unknown. # If a value extracted by is less than minimal of greater than maximal # this parameter is defined, a RRD database will be created and data # parameter is defined as empty, no RRD database will be created. # The 5th parameter is defining if the KPI has to be stored into a RRD # This 4 first parameters have the same signification as for static # Each dynamic KPI is defined by an id and with 5 parameters # with the keyword dynamic and an identifier # Each statistic is identified into the conf file by a line stating # Dynamic KPI are extracted periodically (defined by lay) # This parameter will be evaluate by the command eval of perl. # is an expression defining the postprocessing to # In case of KPI list, each group will be affected to a KPI name. Regexp groups () has to be used to extract the data # is the regular expression extracting information from # rpimonitord to read the content of the executable.1.graph. # Warning: specifying an executable by its absolute name will tell # is not existing, rpimonirotd will try to execute it and will parse # If the file exists, rpimonitord will read its content. # is a file or an executable file within the path. # Only alpha numerical charter and underscore are accepted. # is a string representing the KPI or the list of KPI # Each static KPI is defined by an id and with 4 parameters # is identified into the conf file by a line stating with the keyword # Static KPI are extracted once at rpimonitord startup. # configuration file to add at the end of the list of configuration # the list of configuration files to be loaded. # Specific 'include' keyword is available to add a file at the end of # This part of the configuration file is defining which data to When installing RPiMonitor, check to see if a USB hard drive is being used for storage, then add the line include=/etc/rpimonitor/template/usb_hdd.conf after the line for nf (scroll to the bottom): #
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |