Remove log4j based event reporting
Reported by Greg Schueler | February 16th, 2011 @ 09:47 AM | in Rundeck 1.2
History events are logged via special log4j listener (both
internally, and when running dispatch --noqueue).
this should be removed, and internal history reports done with
internal mechanism.
If external history reports should be supported, it should be added as part of the web API and the CLI tool updated accordingly
Comments and changes to this ticket
-
Deleted User February 16th, 2011 @ 09:49 AM
I agree.
Point of clarification, when you say external history reports...is this the piece where RunDeck can get log4j data from another server?
-
Greg Schueler February 16th, 2011 @ 09:56 AM
by external history reports, I am just referring to the reports sent from outside the server into it via the log4j listener. right now it only comes from "dispatch --noqueue". i.e. the execution happens local to the CLI tool, and a final report is sent to the server. This may be useful, but we should change the mechanism.
-
Deleted User February 24th, 2011 @ 04:46 PM
- State changed from “new” to “resolved”
(from [9ce37f6e6c509770875c3eff8b68210a40675abf]) Remove log4j reportservice code, add report create API endpoint [#205 state:resolved] https://github.com/dtolabs/rundeck/commit/9ce37f6e6c509770875c3eff8...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
People watching this ticket
Greg Schueler
Referenced by
-
205
Remove log4j based event reporting
(from [9ce37f6e6c509770875c3eff8b68210a40675abf])
Remove ...