Skip to content

Configuring a PLOSSYS Distribution Engine/DPF Server

In order to use the Accounting for your PLOSSYS Distribution Engine/DPF instance you need to setup a Filebeat that uploads the data to Elasticsearch. You can setup a new Elasticsearch instance or use an existing one, even one that is currently used to analyze PLOSSYS Output Engine data.

Configuration

  1. In an editor, open the following configuration file:

    /opt/seal/etc/filebeat-dpf.yml

  2. In filebeat.input.paths, add the path to the joblog files and to the accounting log of your PLOSSYS Distribution Engine/DPF installation:

    filebeat.inputs.paths: "/data/dpf/dpfjob*/job.log"
filebeat.inputs.paths: "/data/log/accounting.log"

  3. In an editor, open the main.customer.xml configuration file:

    Seal/applications/server/dpf/templates/main.customer.xml

  4. In Accounting LOGFORMAT, add the following variables, if necessary:

    • JOB_TIMESTAMP_BEGIN

    • JOB_TIMESTAMP_END

    • USED_CHANNELS

    You will need these in the Ingest Pipeline.

  5. Find the tokenizer processor, the name of which starts with Account Info, and add the variables from the LOGFORMAT to the filebeat-dpf.yml.

    Caution - order of attribute names

    You only need the attribute names. You can ignore numbers, special characters and spaces. But mind the order of the attribute names! It must be identical in both files, `main.customer.xml` and `filebeat-dpf.yml`.

However, the syntax may differ, see examples below.

    Example of a LOGFORMAT value

    <accounting
  LOGFORMAT=";%JOB_TIMESTAMP_BEGIN%;%JOB_TIMESTAMP_END%;%JOBID%;%WFNAME%;%ORIGUSERNAME%;%ORIGHOSTNAME%;%USED_CHANNELS%;"
/>

    Example of the corresponding dissect string value

    dissect:
  tokenizer: "Account Info: ';%{JOB_TIMESTAMP_BEGIN};%{JOB_TIMESTAMP_END};%{JOBID};%{WFNAME};%{ORIGUSERNAME};%{ORIGHOSTNAME};%{USED_CHANNELS};'"
  field: jobmessage

  6. In output.elasticsearch.hosts, replace localhost with the URL of the Elasticsearch instance you whish to upload your data to.

    Example of a local host entry

    output.elasticsearch.hosts: "https://10.115.170.126:9200"

  7. Restart Filebeat:

    sudo systemctl restart seal-dpf-filebeat

Logging

If you have installed PLOSSYS Distribution Engine/DPF on a separate management server, you have to set the IP address of the management server for the logging:

  1. On the PLOSSYS Distribution Engine/DPF server, edit the following file:

    /opt/seal/etc/filebeat-operator.yml

  2. In elasticsearch, replace localhost by the host name or IP address of the management server:

    output:
  elasticsearch:
    hosts:
    # - http://<admin_server>:9200
    - "https://<admin_server>:9200"

  3. Save the file.

  4. Restart the PLOSSYS Distribution Engine/DPF filebeat:

    sudo systemctl restart seal-dpf-filebeat
Back to top