Journey Clean up

Login to an environment which has Journey application. On the application dropdown on top left, select Journey. This will open all the options available for Journey.

Click on Clean up on the left menu bar.

Note: User can delete the Journey engine logs and Journey web logs.

Journey Cleanup has below options:

  1. Journey Engine logs
    • Engine logs capture the working of engine application, as per the LOG. Level defined (INFO, WARN, DEBUG), files are created on Roll over bases, with each file size 50MB (can be changed in LOG4j2.xml).
    • Engine Logs hold all information related to exceptions and information related to processing of audience data.

    Path of Engine logs is to be defined under log4j2.xml file under conf folder in Engine Home. Property APP_ROOT_LOG holds the value which defines path for creating logs.

    1. Delete - On clicking on delete button all files, except the current log file, are deleted from the location, once the files are deleted, they cannot be recovered.
    2. Download - User can download journey engine logs. After clicking on Download, a job is triggered and a notification is shown to the user. See below screenshot.  

    To download the files, user has to navigate to the Job queue page, which shows the current status of the action taken. Once the download is available, user can see a link on the job queue page from which they can download the logs.

  2. Journey Web logs
    • Web logs capture the working of web application, as per the LOG. Level defined (INFO, WARN, DEBUG), files are created on Roll over bases, with each file size 50MB (can be changed in LOG4j2.xml).
    • Web Logs hold all information related to exceptions and information related to processing of user activities.

    Path of web logs is to be defined under log4j2.xml file under conf folder in Web Home. Property APP_ROOT_LOG holds the value which defines path for creating logs.

    1. Delete - On clicking on delete button all files, except the current log file, are deleted from the location. Once the files are deleted they cannot be recovered.
    2. Download - User can download journey web logs. After clicking on “Download”, a job is triggered and a notification is shown to the user.

      To download the files, user must navigate to the Job queue page, which shows the current status of the action taken. Once the download is available, user can see a link on the job queue page from which they can download the logs.

    3. File size and File counts - On Clean up page user can see number of files and its size too
  3. Journey upload/output files

    Journey has a property spring.entity.files.upload.defaultPath which is used to configure the path of uploaded files (For example, entrysource files). User can get the count of files or Download the files using this feature.

  4. Kafka logs

    For version 12.1.0.4, only one instance of Kakfa per application is applicable.

    These are the kafka server and controller logs, with different log levels, files re-created on rollover basis. Pattern, logging level and roll over can be changed in log4j.properties file in Config directory.

    For version 12.1.0.4, it is assumed logs are generated on its default location i.e., in logs directory in app home. Perform the following operations on files.
    1. File size and File counts - Display number of files and its size too.
    2. Download – You can download Kakfa logs. After clicking on Download, a job is triggered, and a notification is shown to the user.

      To download the files, user must navigate to the Job queue page, which shows the current status of the action taken. Once the download is available, user can see a link on the job queue page from which they can download the logs.

  5. Zookeeper logs

    For version 12.1.0.4, only one instance of zookeeper per application is applicable.

    These are the zookeeper server logs, with different log levels, files re-created on rollover basis. If app home for kafka and zookeeper are same, we are assuming the logs are getting generated on the same location as of kafka i.e., logs directory in app home path. If the app home for kafka and zookeeper are not same it means zookeeper is standalone in that case we are reading the logs from location mentioned against key zookeeper.log.dir in log4j.properties directory in conf directory.

    Pattern, logging level and roll over can be changed in the same log4j.properties directory. Perform the following operations on files.
    1. File size and File counts - Display number of files and its size too.
    2. Download - User can download zookeeper logs. After clicking on Download, a job is triggered, and a notification is shown to the user.

      To download the files, user must navigate to the Job queue page, which shows the current status of the action taken. Once the download is available, user can see a link on the job queue page from which they can download the logs.