About Logging

View: New views
5 Messages — Rating Filter:   Alert me  

About Logging

by Wesley Hartford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

can LoggingJobHistoryPlugin and LoggingTriggerHistoryPlugin  store the log into database?
If yes, hope that someone tell me how?
If no, are there any plug-ins to store logging in database?
I find that LoggingJobHistoryPlugin and LoggingTriggerHistoryPlugin are suitable to store in database.
For example:
JobToBeFiredMessage - available message data are: Element Data Type Description
0 String The Job's Name.
1 String The Job's Group.
2 Date The current time.
3 String The Trigger's name.
4 String The Triggers's group.
5 Date The scheduled fire time.
6 Date The next scheduled fire time.
7 Integer The re-fire count from the JobExecutionContext.
The default message text is "Job {1}.{0} fired (by trigger {4}.{3}) at: {2, date, HH:mm:ss MM/dd/yyyy}"

7 items above can be stored as 7 columns in database in order to check history whenever.
logging store may be done by scheduler go with job executing.
However, I haven't found the table schema go with Quartz.

long for your answers.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=469788&messageID=558845#558845


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: About Logging

by Wesley Hartford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

No one knows?
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=469788&messageID=559719#559719


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: About Logging

by Wesley Hartford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The current plugins only log the information. You could always extend the Logging..HistoryPlugins and perform your own database persistence.

It may also be possible to incorporate the Log4J logger which provide a data base appender for logging.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=469788&messageID=561635#561635


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: About Logging

by Wesley Hartford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I use the logging history plugin, then parse the logs and stick the data in a warehouse.  That way I'm not adding overhead to persist job information in a database on the running system.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=469788&messageID=561791#561791


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: About Logging

by Wesley Hartford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for your explaination.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=469788&messageID=599494#599494


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

LightInTheBox - Buy quality products at wholesale price!