Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there a way to send or redirect Weblogic (or Fusion Middleware) logging output to a database, without having to write a custom application? All the documentation I've read seem to deal exclusively with files.

share|improve this question

Weblogic is not actually my field, but according to Oracle's documentation, you should be able to send WLS logs to syslog using Log4j Logger, from where it is again possible to forward them to MySQL (and some other) databases.

See here for rsyslog instructions and here for syslog-ng.

This syslog-approach has its benefits, since it is rather trivial to send syslogs from several servers to one central repository and then store them to a database there. Additionally there are front ends available (this to promote one I have used) to ease up analysing.

However this solution probably will not qualify as "without having to write a custom application". Perhaps someone else has better ideas.

share|improve this answer
This seems the only solution that might work, although it's convoluted and requires yet another service. It's disappointing: Weblogic ships all sorts of machinery to talk to databases, and all sorts of machinery to log, and still we need something as old and crusty as as an external syslog daemon just to push these damn messages into a db. – Giacomo Lacava Feb 15 '13 at 0:01

Since Weblogic is capable of utilizing generic Log4j logger facility, it is possible to configure it to send the logs to database.

See here about configuring WLS to use Log4j and here and here about configuring Log4j to direct logs to a database.

This again may not qualify as "without having to write a custom application", but I'm afraid this is as much as out of the box as it gets.

share|improve this answer
The problem with Log4J is that their JDBCAppender supposedly does not log Exceptions, which is a bit of a dealbreaker. – Giacomo Lacava Feb 14 '13 at 23:58

There are 3 types of log sources that an WebLogic application can generate:

  • STDOUT, WebLogic server, HTTP access, transaction and audit logging are using java.util.logging.Logger and can be configured to use log4j easily.
  • application logs - use server logging bridge See:
  • JVM STDOUT (like JVM out of memory errors, thread dumps), that can not be managed by log4j nor WebLogic. Those will always go to a file. (Or I could not find out a way to redirect them)

See also:

Any solution you will chose, you will need to take some time to understand it. Logging can be a very complex task.

share|improve this answer
The logging bridge is the most "out of the box" option, but it doesn't seem to have a db appender. I guess Log4j is the only way. – Giacomo Lacava Feb 14 '13 at 23:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.