You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Justin Dearing <zi...@gmail.com> on 2014/03/04 14:41:26 UTC

Sysinternals Process Monitor appender

Hello,

Wintellect released some code that allows you to send trace messages to
procmon. I wrote an appender that let's you tap into that with log4net. I'm
getting it reviewed and will send wintellect a pull request.

https://github.com/zippy1981/ProcMonDebugOutput/tree/log4net

If I were to make an appender without the dependency on Wintellect's C++
code, could that be added to the log4net built in Appenders?

Regards,

Justin Dearing

Re: Sysinternals Process Monitor appender

Posted by George Chung <ge...@glympse.com>.
Got it. Thanks! Sounds cool!


On Wed, Mar 5, 2014 at 11:12 AM, Justin Dearing <zi...@gmail.com> wrote:

> George,
>
> This does not display messages. This sends messages to Sysinternals
> Process monitor (ProcMon.exe), a tool that display network, file and
> registry activity.
>
> The advantage of sending the messages here instead of the kernel
> DebugOutput mechanism (where DbgView or other can pick them up) is the
> messages would be displayed inline with file, network and registry access.
>
> ProcMon receives and displays the messages.Wintellect's unmnaged  dll send
> messages to procmon. I don't need to actually use wintellects DLL. I can do
> it entirely with PInvoke though.
>
> Justin
>
>
>
> On Wed, Mar 5, 2014 at 1:52 PM, George Chung <ge...@glympse.com> wrote:
>
>> Hi,
>> Just curious. How does Wintellect's app differ from Dbgview (which also
>> displays Trace/OutputDebugWindow messages)?
>>
>> Cheers
>>
>>
>> On Tue, Mar 4, 2014 at 5:41 AM, Justin Dearing <zi...@gmail.com>wrote:
>>
>>> Hello,
>>>
>>> Wintellect released some code that allows you to send trace messages to
>>> procmon. I wrote an appender that let's you tap into that with log4net. I'm
>>> getting it reviewed and will send wintellect a pull request.
>>>
>>> https://github.com/zippy1981/ProcMonDebugOutput/tree/log4net
>>>
>>> If I were to make an appender without the dependency on Wintellect's C++
>>> code, could that be added to the log4net built in Appenders?
>>>
>>> Regards,
>>>
>>> Justin Dearing
>>>
>>
>>
>

Re: Sysinternals Process Monitor appender

Posted by Justin Dearing <zi...@gmail.com>.
George,

This does not display messages. This sends messages to Sysinternals Process
monitor (ProcMon.exe), a tool that display network, file and registry
activity.

The advantage of sending the messages here instead of the kernel
DebugOutput mechanism (where DbgView or other can pick them up) is the
messages would be displayed inline with file, network and registry access.

ProcMon receives and displays the messages.Wintellect's unmnaged  dll send
messages to procmon. I don't need to actually use wintellects DLL. I can do
it entirely with PInvoke though.

Justin



On Wed, Mar 5, 2014 at 1:52 PM, George Chung <ge...@glympse.com> wrote:

> Hi,
> Just curious. How does Wintellect's app differ from Dbgview (which also
> displays Trace/OutputDebugWindow messages)?
>
> Cheers
>
>
> On Tue, Mar 4, 2014 at 5:41 AM, Justin Dearing <zi...@gmail.com>wrote:
>
>> Hello,
>>
>> Wintellect released some code that allows you to send trace messages to
>> procmon. I wrote an appender that let's you tap into that with log4net. I'm
>> getting it reviewed and will send wintellect a pull request.
>>
>> https://github.com/zippy1981/ProcMonDebugOutput/tree/log4net
>>
>> If I were to make an appender without the dependency on Wintellect's C++
>> code, could that be added to the log4net built in Appenders?
>>
>> Regards,
>>
>> Justin Dearing
>>
>
>

Re: Sysinternals Process Monitor appender

Posted by George Chung <ge...@glympse.com>.
Hi,
Just curious. How does Wintellect's app differ from Dbgview (which also
displays Trace/OutputDebugWindow messages)?

Cheers


On Tue, Mar 4, 2014 at 5:41 AM, Justin Dearing <zi...@gmail.com> wrote:

> Hello,
>
> Wintellect released some code that allows you to send trace messages to
> procmon. I wrote an appender that let's you tap into that with log4net. I'm
> getting it reviewed and will send wintellect a pull request.
>
> https://github.com/zippy1981/ProcMonDebugOutput/tree/log4net
>
> If I were to make an appender without the dependency on Wintellect's C++
> code, could that be added to the log4net built in Appenders?
>
> Regards,
>
> Justin Dearing
>

Re: Sysinternals Process Monitor appender

Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-03-06, Justin Dearing wrote:

> On Thu, Mar 6, 2014 at 5:07 AM, Stefan Bodewig <bo...@apache.org> wrote:

>>> If I were to make an appender without the dependency on Wintellect's C++
>>> code, could that be added to the log4net built in Appenders?

>> Would it have any other external dependency?  I don't think we'd want to
>> add any new dependencies to log4net itself.

> There are no dependencies other than the .NET framework and PInvoke..
> Everything happens trough Win32 FileIO. Here is a simple LINQpad example of
> me writing to procmon.

> https://github.com/zippy1981/ProcMon.LINQpad

I'll have a look.

>> Other than that we'd likely need to get some legal issues clear - it is
>> your code and your code alone and you want to grant ot to the ASF -

> I wrote all the code in that LINQpad myself. I used Wintellect's managed
> version and pinvoke.net as references. John from Wintellect has said he is
> ok with me including me code in log4net, but  is willing to sign something
> if someone felt it was necessary. I'm personally willing to keep copyright,
> assign copyright, or hold joint copyright, as per whatever ASF wants.z

I don't think we need any papers signed by John.  The ASF doesn't do
copyright assignement, you'd keep the copyright and grant a license
(using the Apache License in reverse direction) to the ASF.  The ASF
only copyrights the "joined" work of the log4net distribution.

If you'd open a JIRA ticket and attach a patch that is generally enough
to indicate you want to contribute your code.  This is via section 5 of
http://www.apache.org/licenses/LICENSE-2.0

Doing away with legaleese.

> Its not a lot of code to write, so I'd rather debate a patch than code I
> will theoretically write. You guys use SVN. Should I just email an actual
> patch to the list? If I were to import the svn repo as a git repo on
> github, could you guys generate a patch from that to allow for back and
> forth feedback? Is there a formal vote?

First open a JIRA ticket as our point of reference.  We can work with
patches attached to the ticket or with pull requests, whatever suits you
better.

There is a github mirror of the log4net repo at
https://github.com/apache/log4net and I think we've taken all setup
steps necessary for using some Apache side integration of github PRs
with Apache JIRA tickets and mailing lists.  IIUC you use the JIRA
ticket number (LOG4NET-000) inside you PR comment and it will
automatically be linked with the ticket[1] - but you'd be the first
person trying this out for log4net :-)

Stefan

[1] http://blogs.apache.org/infra/entry/improved_integration_between_apache_and


Re: Sysinternals Process Monitor appender

Posted by Justin Dearing <zi...@gmail.com>.
Stefan.




On Thu, Mar 6, 2014 at 5:07 AM, Stefan Bodewig <bo...@apache.org> wrote:

> > If I were to make an appender without the dependency on Wintellect's C++
> > code, could that be added to the log4net built in Appenders?
>
> Would it have any other external dependency?  I don't think we'd want to
> add any new dependencies to log4net itself.
>
There are no dependencies other than the .NET framework and PInvoke..
Everything happens trough Win32 FileIO. Here is a simple LINQpad example of
me writing to procmon.

https://github.com/zippy1981/ProcMon.LINQpad



> Other than that we'd likely need to get some legal issues clear - it is
> your code and your code alone and you want to grant ot to the ASF -

I wrote all the code in that LINQpad myself. I used Wintellect's managed
version and pinvoke.net as references. John from Wintellect has said he is
ok with me including me code in log4net, but  is willing to sign something
if someone felt it was necessary. I'm personally willing to keep copyright,
assign copyright, or hold joint copyright, as per whatever ASF wants.z

> but personally I don't see any reason to not include it.  I'm certainly not
> the only member of the team.
>

Its not a lot of code to write, so I'd rather debate a patch than code I
will theoretically write. You guys use SVN. Should I just email an actual
patch to the list? If I were to import the svn repo as a git repo on
github, could you guys generate a patch from that to allow for back and
forth feedback? Is there a formal vote?

Justin

Re: Sysinternals Process Monitor appender

Posted by Stefan Bodewig <bo...@apache.org>.
Sorry for the delay, Justin

On 2014-03-04, Justin Dearing wrote:

> If I were to make an appender without the dependency on Wintellect's C++
> code, could that be added to the log4net built in Appenders?

Would it have any other external dependency?  I don't think we'd want to
add any new dependencies to log4net itself.

Other than that we'd likely need to get some legal issues clear - it is
your code and your code alone and you want to grant ot to the ASF - but
personally I don't see any reason to not include it.  I'm certainly not
the only member of the team.

Stefan