COmanage Developers List

[Scott Koranda <>]

A followup thought...

----- Forwarded message from Scott Koranda 
<>
 -----

Date: Mon, 19 Feb 2018 16:48:21 -0600
From: Scott Koranda 
<>
To: 

Subject: Re: Campus Success component logging requirements

> Regarding the component logging requirements coming out of the TIER
> Campus Success Meeting...
> 
> On last week's call we learned that the desired format is
> 
> ComponentName, LogfileName, Env, UserDefinedEnvironmentVar
> 
> where Env is one of Prod, Dev, or Test and any dot in a LogfileName
> should be replaced by a '-'.

I am also wondering...

The command 'docker run' supports the option

--log-opt tag="<almost anything>"

See

https://docs.docker.com/config/containers/logging/log_tags/

The option is also suppored in Docker compose files. See

https://docs.docker.com/compose/compose-file/#logging

Is the right approach then to just tell deployers to use those options
and tag their container log files as they see fit?

We will have a few containers where there is more than one process
logging, like for COmanage where we have Apache HTTP Server,
Supervisord, Shibboleth SP, and COmanage Registry itself, so it might
make sense to make sure those log lines are appropriately prefixed in
some way, but shouldn't things like 'Env' or 'UserDefinedEnvVariable'
just be set by the deployer for the container using the mechanism above?

Thanks,

Scott K

----- End forwarded message -----