Add logs about jongo

[ihr]

Some other loggers worth mentioning:

• log4j 2
• Logback
• blitz4j

[bguerout]

Should be added in v0.4 with an agnostic interface (eg. LogListener)

Eg.

class LogbackListener implements LogListener(){

   Logger logger = LoggerFactory.getLogger(...);

   void log(String message, Level level){
      logger.debug(message);
   }
}
...
new Jongo(..., new LogbackListener());

JUL can be a built-in implementation

[ihr]

Out of interested why not use slf4j-api and then have the actual loggin implementation provided ?

[bguerout]

Well, this is a good question.

If a log framework is chosen instead of LogListener, it should definitely be SLF4J.

Nevertheless, since the beginging we are trying to minimize as far as we can project dependencies.
Jongo v0.1 and 0.2 have only one dependency : Jackson, v0.3 will have two : Jackson and Bson4jackson.
SLF4J is a transitive dependency of many other projects and here begin Maven version conflict hell.

Is LogListener interface not an elegant alternative to you ?

[bguerout]

BTW, as JUL is the built-in JDK logging API, we could provide a JUL implementation of LogListener without any dependency

[ihr]

I see jongo as being used mainly on server side, so I don't think that having a reasonable number of well chosen dependencies will harm anyone. Furthermore, SLF4J-API has zero dependencies and is a more transparent approach than providing a custom LogListener which is a bit intrusive. I'm not a huge fan of JUL since it's environment is closed and I think logging merits an open source environment. Just a side note about Jackson, there seems to be a really nasty regression #113 so I hope jongo has a good testbed.

[codeallthethingz]

I'd rather there be no additional logging dependencies in Jongo. We are using log4j, and if you decide that Jongo uses SLF4J we'll have to add the SLF4J bridge, I think your existing callback solution is elegant and all that is required.

[ihr]

Right. If I'm using slf4j does this make the solution less elegant (if yes, to what degree?)? Or is it that as long as you are using log4j directly the solution remains elegant? If that's the case, let me know when you switch to another framework so that I can calibrate my watch. Say what is the problem with using a slf4j?

[geronimo-iia]

No, it's not less elegant. Using callback permit us to choose how to log and what framework to use. Another good star its to avoid maven dependencie hell :-)

[ihr]

Using slf4j-api also lets you choose the implementation that fits best for you, avoiding dependency hell. If you want to develop your own logging framework and come up with some super cool functionality then go ahead and simply implement an slf4j bridge. And if you do that maybe you can share your solution with the rest of the world and make it a better place for each and every one of us! :-)

[geronimo-iia]

@ihr Of course you could !!
Thanks for the joke

[ihr]

@geronimo-iia Glad to be of help!

[SanderDN]

Is this something that's still on any roadmap?
This is quite urgent, since we have no way to log which queries are performed. Any attempts to show mongo java driver logging, only show technical info, and no actual queries.

Any way to currently show queries is much appreciated.

[candidtim]

For information, as of Mongo 3, its Java Driver supports logging with SLF4J, quite well configurable: http://mongodb.github.io/mongo-java-driver/3.2/driver/reference/management/logging/ . This probably makes this issue obsolete.

[SanderDN]

Configuring the mongodb logging will provide us with some logging:

19:09:39.283 DEBUG org.mongodb.driver.protocol.query - Sending query of namespace myapp.collection on connection [connectionId{localValue:2, serverValue:9446}] to server myserver:27017
19:09:39.328 DEBUG org.mongodb.driver.protocol.query - Query completed

But this does not show us which query was actually performed (query text).

[peter-moore-surverysampling]

Bump! As SanderDN mentions, the Mongo driver logging is entirely inadequate. It shows that a query was run, but not the interesting details about that query.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.