Enabling activity logging and setting up Activity Trends

You enable activity logging and set up Activity Trends in the Configuration Settings document. First, you enable activity logging to gather data for the selected server tasks.

About this task

The first time you start Activity Trends, the system must run and collect data for 24 hours before you can work with the data. Then you specify how to collect the Activity Trends and create the Activity Trends database (ACTIVITY.NSF), which is stored, by default, in the Domino® data directory.


  1. From the Domino® Administrator, click the Configuration tab, expand the Server section, and click Configurations.
  2. Select the server, and click Edit Configuration or Add Configuration.
  3. Click the Activity Logging tab, and enable the check box Activity logging is enabled.
  4. Under Server Activity Logging Configuration, complete these fields:
    Table 1. Server Activity Logging Configuration fields
    Field Action
    Enabled logging types Select the server tasks to use to produce activity logging data.

    For Activity Trends, enable all tasks except Domino®.MAIL. At a minimum, you must enable Domino®.Notes.Session and Domino®.Notes.Database.

    Checkpoint interval Enter the number of minutes to wait between the creation of checkpoint records. The default is 15 minutes.
    Log Checkpoint at Midnight Check Yes to log ongoing session activity at midnight. This is required for Activity Trends.

    You must enable this field to enable Activity Logging.

    Log Checkpoints for Prime Shift Check Yes and then specify the prime shift interval to log checkpoints for the prime shift.

    You must enable this field to enable Activity Logging.

    Prime Shift Interval Specify the start and end time of prime shift. Set the interval on the hour.
  5. Click the Activity Trends tab, and complete the following fields on the Basics tab:
    Table 2. Basics tab
    Field Action
    Enable activity trends collector Click yes to run the Activity Trends Collector.

    Activity Trends Collector uses the raw data from activity logging and prepares it for use with Activity Trends.

    Activity trends collector database path Enter the name and path of the database where Activity Trends data is stored if you want to change this. The default is activity.nsf.
    Time of day to run activity trends collector Enter a time. The default is 3:23 AM. Schedule the Activity Trends Collector to run after the Catalog task runs. By default, the Catalog task runs at 1 AM.
    Days of the week to collect observations Select the days for which you want to collect observations. The default is Monday through Friday.
  6. Under Activity Trends Data Profile Options, keep the Use defaults field enabled. If you choose not to use the defaults, complete these fields.
    Table 3. Activity Trends Data Profile Options
    Field Action
    Trends cardinal interval Enter the number of recent observations you want to use. The default is 10.

    When computing trended values, recent observations are weighted the most. For example, if you select Monday through Friday in the Day of the week to collect observations field and use the default 10 in the Trends cardinal interval field, the trended values will include two weeks of observations (five days each week).

    Note: If you know there has been a recent change in user activity, you may choose not to use trended values.
    Observation time bucket (seconds) Specify the time in seconds for one bucket. The default is 300.

    The observation time controls how many buckets you will have for one 24-hour observation period.

    Maximum observation list size Specify the maximum length of time data is kept in the Trends database before it is overwritten with new data. The default is 366, the number of days in a leap year.
    Trends history interval Choose one:
    • Daily
    • Weekly (default)
    • Monthly
    • Trend Interval
  7. Click the Retention tab. Keep the Use defaults field enabled. Documents are overwritten after the retention period expires. The defaults are:
    • Server history -- 366 days
    • Server observations --15 days
    • Database observations -- 10 days
    • User observations -- 10 days
    • Connection observations -- 10 days
    • Inactive database trends -- 10 days
    • Inactive user trends -- 28 days
    • Inactive connection trends -- 28 days
    • Run log -- 20 days
  8. Click the Proxy Data tab, and enter the names of the databases containing activity data to search.
  9. Click Save and Close.