Jan 5, 2021

    Changing the frequency of the Pulse Elasticsearch indices

    This article is only relevant if your server is running short of disk space and that you want to reduce the size of the Pulse Elasticsearch cluster.

    Before going further in this article, you must have read and understood the following article:

    By default, the pulse-server-state index is split by month. A new index will be created per month (pulse-server-state-2021-01, pulse-server-state-2021-02…).

    If you are short in memory and instead of keeping only the last month of the pulse-server-state, you would like to keep the last 7 days. You will need to change the frequency of the pulse-server-state.

    To do that, go to the <Pulse folder>/conf/Pulse.cfg file, update the ServerStateIndexPattern value from yyyy-MM to yyyy-MM-dddd.

    Save the file end then restart the Pulse Application Server.

    There is one setting in the Pulse.cfg per index:

    Name Default value Index
    ServerStateIndexPattern yyyy-MM pulse-server-state
    TM1TopIndexPattern yyyy-MM-dd pulse-tm1-top
    TM1ServerLogIndexPattern yyyy-MM-dd pulse-tm1-server-log
    ChoreProcessHistoryIndexPattern yyyy pulse-chore-process-history
    TM1ObjectHistoryIndexPattern yyyy pulse-tm1-object-history
    TM1UserHistoryIndexPattern yyyy pulse-tm1-user-history
    TM1SessionLogIndexPattern yyyy pulse-tm1-session-history
    AlertIndexPattern yyyy pulse-alert-history
    TM1ServerActionIndexPattern yyyy pulse-server-action-history

    The pulse-tm1-client-history is a unique index that has only the list of users.

    Related content

    Loading related content