[ man7.org ](../../../index.html) > Linux > [ man-pages ](../index.html) |  [ Linux/UNIX system programming training ](http://man7.org/training/)  
---|---  
  
* * *

#  pmlogger_daily_report(1) — Linux manual page

NAME  |  SYNOPSIS  |  DESCRIPTION  |  OPTIONS  |  PCP ENVIRONMENT  |  SEE ALSO  |  COLOPHON   
---  
|  
      
    
    _PMLOGGER_DAILY_REPORT_(1) General Commands Manual _PMLOGGER_DAILY_REPORT_(1)
    

##  NAME  top

    
    
           **pmlogger_daily_report** - write Performance Co-Pilot daily summary
           reports
    

##  SYNOPSIS  top

    
    
           **$PCP_BINADM_DIR/pmlogger_daily_report**[**-ApV?**]  [**-a** _archivefile_]
           [**-f** _outputfile_] [**-h** _hostname_] [**-l** _logfile_] [**-o** _directory_] [**-t**
           _interval_]
    

##  DESCRIPTION  top

    
    
           **pmlogger_daily_report** writes daily performance summary reports,
           much like those produced by **sadc**(1) and the [sa2(8)](../man8/sa2.8.html) utility.
    
           All of the command line arguments are optional and intended to be
           self explanatory.
    
           By default, the reports are not generated, but if the _pcp-_
           _zeroconf_ package has been installed (there will be files in
           **$PCP_VAR_DIR/config/pmlogconf/zeroconf**) then the necessary
           metrics will have been included in the default [pmlogger(1)](../man1/pmlogger.1.html)
           configuration file and the reports will be generated.
    
           The reports are generated (by default) soon after midnight, once
           [pmlogger_daily(1)](../man1/pmlogger_daily.1.html) has completed the merging of any partal
           archives to generate one archive for yesterday's activity.
    
           Each performance summary report is named **sar** _XX_ (where _XX_ is
           yesterdays day-of-the-month).  The _outputfile_ may be changed with
           the **-f** option.  The report will be written to the _$PCP_LOG_DIR/sa_
           directory by default, but this may be changed with the **-o** option
           to a different _directory_.
    
           Note that there are suffciently flexible command line options for
           **pmlogger_daily_report** to be used to read any _archivefile_ and
           write the report to any output directory.
    
           If the **-a** option is not given, the default input _archivefile_ is
           _$PCP_ARCHIVE_DIR/HOSTNAME/YYYYMMDD_ , where _HOSTNAME_ defaults to
           the local hostname (unless changed with the **-h** option) and
           _YYYYMMDD_ is the base name of yesterdays merged archive, as
           produced by [pmlogger(1)](../man1/pmlogger.1.html) and [pmlogger_daily(1)](../man1/pmlogger_daily.1.html).  If _archivefile_ is
           a directory, then **pmlogger_daily_report** will use all PCP archives
           found in that directory to write the report (this is known as
           multi-archive mode, and may be considerably slower than
           specifying a single archive as the input).
    
           The reports themselves are created by the [pmrep(1)](../man1/pmrep.1.html) utility using
           its default configuration file, see [pmrep.conf(5)](../man5/pmrep.conf.5.html).  The [pmrep(1)](../man1/pmrep.1.html)
           configuration entries used to write the reports is currently
           hardwired into the **pmlogger_daily_report** script.
    
           Finally, the input archives must contain sufficient metrics as
           needed by [pmrep(1)](../man1/pmrep.1.html) to write the report.  On platforms that
           support it, the _pcp-zeroconf_ package configures PCP logging as
           required for this - hence **pmlogger_daily_report** should be used
           with the [pmlogger(1)](../man1/pmlogger.1.html) configuration that is set up by **pcp-**
           **zeroconf**.  As the name suggests, **pcp-zeroconf** requires no
           additional configuration after installation in order t