How to do logging of transferred data locally

TABLE OF CONTENTS

• Introduction
• How to set it up

Introduction

The actual schedule data being transferred is subject to strict security rules and shall at no point be accessible by anyone during a transfer in the IDE service. Or rather: The representatives of the IEA have the option of turning on local logging of transferred data, as well as API traffic to/from host system, so that they can convey these logs to support personnel relating to their "half" of the transfer.

Such logs can be invaluable to shed light on exactly what was transferred, so that the root cause of any unexpected behavior can be uncovered. 

How to set it up

In the upper right corner of the Desktop Client, you find a “cogwheel” that opens the settings for local file Logging:

Screenshot showing where to enter the path where the log files should be stored (1) 

You need to tick the box for “Enable HTTP Traffic Logs (2) and specify a path (1) where logs should reside on your local machine.

The logs may over time use a substantial amount of disc space, so the button (3) allows you to permanently delete the log files.

If you wish to specify (default unchecked) a retry of the failed Http calls, you may check the option (4).

Let’s look at a specific example of a generated log file for this transfer (IEAId=1151 and TransferId=680848):

The auto-generated folder name for these log files is:

IEA-1151_680848

In order to attach this folder content (blue frame) to a support ticket, you first need to zip it (red frame):

NOTE: The subfolders for this folder are named according to the host systems used for upload and download as seen below (red frames):