This article covers the Peering Manager’s remote logging feature which can be used with on-premise setups. With this, we are able to inspect its application logs without the need for direct access to the machine it is running on.


Content


Logged Data

We only log the output of the application itself, no other information from the system will be included in the transmitted logs.

Basically everything you can see directly on the server when inspecting the Peering Manager’s logs will be mirrored and sent to Google Cloud Logging.


Requirements

The server the Peering Manager is running on needs access to the internet, more explicitly to https://logging.googleapis.com.

In addition to that, a credentials file is needed to authenticate the application against the above mentioned API. To receive such a credentials file, please get in touch with your technical account manager.


Setup

Enabling the remote logging requires the following settings in the Peering Manager’s configuration file (config.yaml):

ServiceConfig:
  DeploymentConfig:
    GCPLogging:
      Enabled: true
      CredentialsPath: './credentials.json' # Adjust this to the actual path and file name of the file
      InstanceID: 'my-peering-manager'      # Optional, if skipped the hostname of the system will be used
YAML

Once you added the properties to the configuration file, you need to restart the service for the changes to take effect.


Change Log

Document Owner: @a user

Version

Date

Person

Description

1.0.0

05.11.2021

@a user

Initial version