Clientlog Configuration

Table of Contents

Introduction
Default Values
The Log Service Ecosystem
Clientlog Events
Event Bus Configuration
Configuration
- Environment Variables
- YAML Example

Introduction

The Infinite Scale clientlog service is responsible for composing machine-readable notifications for clients. Clients are apps and web interfaces.

Default Values

The clientlog service listens on port 9260 by default.

The Log Service Ecosystem

Log services like the activitylog, clientlog, sse and userlog are responsible for composing notifications for a certain audience.

Log services and their tasks
activitylog ¹	This service stores events per resource. These can be retrieved to show item activities.
clientlog	This service composes machine-readable messages, so clients can act without the need to query the server.
eventhistory	This service stores events and allows other services to retrieve them via an event ID.
sse	This service is only responsible for sending these messages. It does not care about their form or language.
userlog ²	This service translates and adjusts messages to be human-readable.

Log services and their tasks

activitylog ¹

This service stores events per resource. These can be retrieved to show item activities.

clientlog

This service composes machine-readable messages, so clients can act without the need to query the server.

eventhistory

This service stores events and allows other services to retrieve them via an event ID.

sse

This service is only responsible for sending these messages. It does not care about their form or language.

userlog ²

This service translates and adjusts messages to be human-readable.

Services may depend on each other:

The activitylog service requires the eventhistory service.
The userlog service is configured by default to use both the eventhistory and sse service. It can be configured to use both, the one, or the other.

Clientlog Events

The messages the clientlog service sends are intended for use by clients, not by users. The client might for example be informed that a file has finished post-processing. With that, the client can make the file available to the user without additional server queries.

Event Bus Configuration

The Infinite Scale event bus can be configured by a set of environment variables.

If you are using a binary installation as described in Minimal Bare Metal Deployment or Bare Metal with systemd, the address of the event bus OCIS_EVENTS_ENDPOINT is predefined as localhost address without the need for further configuration, but changeable on demand.
In case of an orchestrated installation like with Docker or Kubernetes, the event bus must be an external service for scalability like a Redis Sentinel cluster or a key-value-store NATS JetStream. Both named stores are supported and also used in Caching and Persistence. The store used is not part of the Infinite Scale installation and must be separately provided and configured.
Note that from a configuration point of view, caching and persistence are independent of the event bus configuration.

Note that for each global environment variable, a service-based one might be available additionally. For precedences see Environment Variable Notes. Check the configuration section below.

Without the aim of completeness, see the list of environment variables to configure the event bus:

Envvar Description

Envvar	Description
`OCIS_EVENTS_ENDPOINT`	The address of the event system.
`OCIS_EVENTS_CLUSTER`	The clusterID of the event system. Mandatory when using NATS as event system.
`OCIS_EVENTS_ENABLE_TLS`	Enable TLS for the connection to the events broker.
`OCIS_INSECURE`	Whether to verify the server TLS certificates.
`OCIS_EVENTS_AUTH_USERNAME`	The username to authenticate with the events broker.
`OCIS_EVENTS_AUTH_PASSWORD`	The password to authenticate with the events broker.

OCIS_EVENTS_ENDPOINT

The address of the event system.

OCIS_EVENTS_CLUSTER

The clusterID of the event system. Mandatory when using NATS as event system.

OCIS_EVENTS_ENABLE_TLS

Enable TLS for the connection to the events broker.

OCIS_INSECURE

Whether to verify the server TLS certificates.

OCIS_EVENTS_AUTH_USERNAME

The username to authenticate with the events broker.

OCIS_EVENTS_AUTH_PASSWORD

The password to authenticate with the events broker.

Configuration

Environment Variables

The clientlog service is configured via the following environment variables. Read the Environment Variable Types documentation for important details. Column IV shows with which release the environment variable has been introduced.

master + Rolling 6.6.1

Deprecation notes for the clientlog service
Deprecation Info	Deprecation Version	Removal Version	Deprecation Replacement
CLIENTLOG_REVA_GATEWAY removed for simplicity.	6.0	next-prod

Environment variables for the clientlog service
Name	IV	Type	Default Value	Description
`OCIS_TRACING_ENABLED` `CLIENTLOG_TRACING_ENABLED`	5.0	bool	false	Activates tracing.
`OCIS_TRACING_TYPE` `CLIENTLOG_TRACING_TYPE`	5.0	string		The type of tracing. Defaults to '', which is the same as 'jaeger'. Allowed tracing types are 'jaeger' and '' as of now.
`OCIS_TRACING_ENDPOINT` `CLIENTLOG_TRACING_ENDPOINT`	5.0	string		The endpoint of the tracing agent.
`OCIS_TRACING_COLLECTOR` `CLIENTLOG_TRACING_COLLECTOR`	5.0	string		The HTTP endpoint for sending spans directly to a collector, i.e. http://jaeger-collector:14268/api/traces. Only used if the tracing endpoint is unset.
`OCIS_LOG_LEVEL` `CLIENTLOG_USERLOG_LOG_LEVEL`	5.0	string		The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.
`OCIS_LOG_PRETTY` `CLIENTLOG_USERLOG_LOG_PRETTY`	5.0	bool	false	Activates pretty log output.
`OCIS_LOG_COLOR` `CLIENTLOG_USERLOG_LOG_COLOR`	5.0	bool	false	Activates colorized log output.
`OCIS_LOG_FILE` `CLIENTLOG_USERLOG_LOG_FILE`	5.0	string		The path to the log file. Activates logging to this file if set.
`CLIENTLOG_DEBUG_ADDR`	5.0	string	127.0.0.1:9260	Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.
`CLIENTLOG_DEBUG_TOKEN`	5.0	string		Token to secure the metrics endpoint.
`CLIENTLOG_DEBUG_PPROF`	5.0	bool	false	Enables pprof, which can be used for profiling.
`CLIENTLOG_DEBUG_ZPAGES`	5.0	bool	false	Enables zpages, which can be used for collecting and viewing in-memory traces.
`OCIS_JWT_SECRET` `CLIENTLOG_JWT_SECRET`	5.0	string		The secret to mint and validate jwt tokens.
`OCIS_REVA_GATEWAY` `CLIENTLOG_REVA_GATEWAY` Deprecation Note	5.0	string	com.owncloud.api.gateway	CS3 gateway used to look up user metadata
`OCIS_EVENTS_ENDPOINT` `CLIENTLOG_EVENTS_ENDPOINT`	5.0	string	127.0.0.1:9233	The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.
`OCIS_EVENTS_CLUSTER` `CLIENTLOG_EVENTS_CLUSTER`	5.0	string	ocis-cluster	The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.
`OCIS_INSECURE` `CLIENTLOG_EVENTS_TLS_INSECURE`	5.0	bool	false	Whether to verify the server TLS certificates.
`OCIS_EVENTS_TLS_ROOT_CA_CERTIFICATE` `CLIENTLOG_EVENTS_TLS_ROOT_CA_CERTIFICATE`	5.0	string		The root CA certificate used to validate the server’s TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.
`OCIS_EVENTS_ENABLE_TLS` `CLIENTLOG_EVENTS_ENABLE_TLS`	5.0	bool	false	Enable TLS for the connection to the events broker. The events broker is the ocis service which receives and delivers events between the services.
`OCIS_EVENTS_AUTH_USERNAME` `CLIENTLOG_EVENTS_AUTH_USERNAME`	5.0	string		The username to authenticate with the events broker. The events broker is the ocis service which receives and delivers events between the services.
`OCIS_EVENTS_AUTH_PASSWORD` `CLIENTLOG_EVENTS_AUTH_PASSWORD`	5.0	string		The password to authenticate with the events broker. The events broker is the ocis service which receives and delivers events between the services.
`OCIS_SERVICE_ACCOUNT_ID` `CLIENTLOG_SERVICE_ACCOUNT_ID`	5.0	string		The ID of the service account the service should use. See the 'auth-service' service description for more details.
`OCIS_SERVICE_ACCOUNT_SECRET` `CLIENTLOG_SERVICE_ACCOUNT_SECRET`	5.0	string		The service account secret.

YAML Example

Note the file shown below must be renamed and placed in the correct folder according to the Configuration File Naming conventions to be effective.
See the Notes for Environment Variables if you want to use environment variables in the yaml file.

master + Rolling 6.6.1

# Autogenerated
# Filename: clientlog-config-example.yaml

tracing:
  enabled: false
  type: ""
  endpoint: ""
  collector: ""
log:
  level: ""
  pretty: false
  color: false
  file: ""
debug:
  addr: 127.0.0.1:9260
  token: ""
  pprof: false
  zpages: false
grpc_client_tls: null
token_manager:
  jwt_secret: ""
reva_gateway: com.owncloud.api.gateway
events:
  endpoint: 127.0.0.1:9233
  cluster: ocis-cluster
  tls_insecure: false
  tls_root_ca_certificate: ""
  enable_tls: false
  username: ""
  password: ""
service_account:
  service_account_id: ""
  service_account_secret: ""