Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log format: traces to stdout should have the same format as those to file #2609

Closed
AlvaroVega opened this issue Oct 20, 2016 · 3 comments
Closed
Labels
Milestone

Comments

@AlvaroVega
Copy link
Member

-fg argument is used by docker image:
https://github.com/telefonicaid/fiware-orion/blob/master/docker/Dockerfile#L115

log format, according with https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/admin/logs.md#log-format, by default should be:

time=2014-07-18T16:39:06.265Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=contextBroker.cpp[1217]:main | msg=Orion Context Broker is running

instead of

INFO@08:27:43  connectionOperations.cpp[79]: Database Operation Successful (query: {})
@AlvaroVega AlvaroVega changed the title BUG (docker) -fg argument implies lost of log format BUG command line option: -fg argument implies lost of log format Oct 20, 2016
@iariasleon
Copy link
Contributor

iariasleon commented Oct 20, 2016

-fg parameter is to start the broker in Foreground. It is mainly used for debugging. I think, the dockerfile should not have this parameter.

@fgalan fgalan added the backlog label Oct 21, 2016
@fgalan fgalan modified the milestones: 1.5.0, 1.6.0 Oct 25, 2016
@kzangeli kzangeli changed the title BUG command line option: -fg argument implies lost of log format log format: traces to stdout should have the same format as those to file Nov 3, 2016
@fgalan
Copy link
Member

fgalan commented Nov 4, 2016

Implemented by PR #2645. Please @AlvaroVega have a look with newest docker version ("latest" tag) to check that now is ok with you.

@AlvaroVega
Copy link
Member Author

@fgalan it works fine!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants