JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

Log files include data that are considered being sensitive by a number of users. This includes

  • Hostnames, IP Addresses
  • Ports
  • Accounts
  • Database Names
  • etc.

There are situations when log files are forward to a 3rd party, for example to the SOS Ticketing System or to a public forum to receive community support.

JS7 offers to anonymize logs by replacing sensitive data with placeholders.

Log Anonymizer

Locations

Anonymization is available from a Java implementation and is invoked from the a shell script in the following locations:

Invocation of Log Anonymizer for Unix
# JOC Cockpit
/opt/sos-berlin.com/js7/joc/jetty/bin/anonymize-logs.sh

# Controller
/opt/sos-berlin.com/js7/controller/bin/anonymize-logs.sh

# Agent
/opt/sos-berlin.com/js7/agent/bin/anonymize-logs.sh
Invocation of Log Anonymizer for Windows
@rem JOC Cockpit
C:\Program Files\sos-berlin.com\js7\joc\jetty\bin\anonymize-logs.cmd

@rem Controller
C:\Program Files\sos-berlin.com\js7\controller\bin\anonymize-logs.cmd

@rem Agent
C:\Program Files\sos-berlin.com\js7\agent\bin\anonymize-logs.cmd

Usage

Invocation of Log Anonymizer for Unix
Usage: log-anonymizer.sh [Options] [Switches]

  Options:
    --log-file=<log-file>       | optional: location of the log file that should be anonymized; files, folders and wildcards can be specified
    --rules-file=<rules-file>   | optional: the path to a file holding rules for anonymization
    --export-rules=<rules-file> | optional: the path to a file to which default rules are exported




  • No labels