Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Remove log4j based event reporting

#205

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

Reported by Greg Schueler · February 16th, 2011 @ 09:47 AM

State: resolved
Milestone: Rundeck 1.2
Assigned to: nobody

Activity

  1. Deleted User
    Deleted User

    I agree.

    Point of clarification, when you say external history reports...is this the piece where RunDeck can get log4j data from another server?

    February 16th, 2011 @ 09:49 AM

  2. Greg Schueler
    Greg Schueler

    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.

    February 16th, 2011 @ 09:56 AM

  3. Deleted User
    Deleted User
    • State changed from new to resolved

    February 24th, 2011 @ 04:46 PM

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.