Come on @Daan Hoogland <daan.hoogl...@gmail.com>, that PR has nothing to do with what he wants to do. If the matter was to simply acquire log entries, he could hook a custom Log Appender in Log4J to process and store the log entries in some way that is usable for him. From what I understood the scope is bigger (specially when we consider the expression "real-time monitoring").
I see a few challenges: - Extracting/consolidating log entries from System VMs(VRs, console proxy, and storage system VM). - Real time performance meeting (In some places, the method ACS uses right now cannot be considered real time) - Extend the event bus that we have to be CADF compliant (for all resources managed by CloudStack) On Tue, Jan 29, 2019 at 6:42 AM Daan Hoogland <daan.hoogl...@gmail.com> wrote: > I forgot to mention the cloudstack event model. You'll have to look at that > as well > > On Tue, Jan 29, 2019 at 9:41 AM Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > H Nikolaos, > > have a look at https://github.com/apache/cloudstack/pull/2992. it was > > -1'd but i think it would fit your ideas. have a look see if you can add > > your thoughts to that and I'll be happy to look at PRs to the base branch > > of that one. > > regards > > > > On Tue, Jan 29, 2019 at 8:41 AM Nikolaos Dalezios <dale...@gmail.com> > > wrote: > > > >> Hello dev team, > >> My name is Nikos Dalezios and I am currently working on my MSc thesis > >> "Cloud log forensics - Log unification - the CADF case". I have just > >> forked > >> the code and I am studying at the moment various aspects of CloudStack > and > >> would like to implement CADF logging. > >> > >> Any suggestions or help is always acceptable. > >> > >> Thank you > >> > > > > > > -- > > Daan > > > > > -- > Daan > -- Rafael Weingärtner
