Problem with NLog log

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with NLog log

delfo
hi,
i have an application that produce a log file similar to this

Debug   10   12472   2013-09-26 21:42:57.1402  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.1582  Program                  It's gonna happen!!:09.42.57.164238
Debug   10   12472   2013-09-26 21:42:57.3652  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.3652  Program                  It's gonna happen!!:09.42.57.365266
Debug   10   12472   2013-09-26 21:42:57.5662  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.5662  Program                  It's gonna happen!!:09.42.57.566289
Debug   10   12472   2013-09-26 21:42:57.7673  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.7673  Program                  It's gonna happen!!:09.42.57.767314
Debug   10   12472   2013-09-26 21:42:57.9683  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.9683  Program                  It's gonna happen!!:09.42.57.968341

using this layout setting
              layout="${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}"

the problem is that when i try to load this file under the Layoutpattern options i cannot reach to find any of NLog keywords even the ComboBox shows 2 NLog entries.
What am i wrong ??
Thanks in advance
Stefano
Reply | Threaded
Open this post in threaded view
|

AW: Problem with NLog log

Ulrich
Administrator

Hi Stefano,

 

the current version of Log4View only offers log4net keywords.

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

Mit freundlichen Grüßen / Yours sincerely

 

Ulrich Proeller

PROSA GmbH

 

Greinerstraße 23a

86316 Friedberg

Fon: +49 821 45061081

Fax: +49 821 45061082

Mobile: +49 170 5417282

www.prosa-gmbh.de

[hidden email]


PROSA Gesellschaft für System und Anwendungsentwicklung mbH

GF: Ulrich Proeller, Ulrike Proeller

AG Augsburg, HRB 17165

Ust.-Id. Nr: DE202375536

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Donnerstag, 26. September 2013 21:55
An: Ulrich Proeller
Betreff: Problem with NLog log

 

hi,
i have an application that produce a log file similar to this

Debug   10   12472   2013-09-26 21:42:57.1402  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.1582  Program                  It's gonna happen!!:09.42.57.164238
Debug   10   12472   2013-09-26 21:42:57.3652  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.3652  Program                  It's gonna happen!!:09.42.57.365266
Debug   10   12472   2013-09-26 21:42:57.5662  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.5662  Program                  It's gonna happen!!:09.42.57.566289
Debug   10   12472   2013-09-26 21:42:57.7673  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.7673  Program                  It's gonna happen!!:09.42.57.767314
Debug   10   12472   2013-09-26 21:42:57.9683  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.9683  Program                  It's gonna happen!!:09.42.57.968341

using this layout setting
              layout="${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}"

the problem is that when i try to load this file under the Layoutpattern options i cannot reach to find any of NLog keywords even the ComboBox shows 2 NLog entries.
What am i wrong ??
Thanks in advance
Stefano


If you reply to this email, your message will be added to the discussion below:

http://forum.log4view.com/Problem-with-NLog-log-tp20.html

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: AW: Problem with NLog log

delfo
HI,
thanks for the reply.
This is exactly what i have done without success.
Please try to create a simple text log file with the sample data that i write in previous message and use this string
 
${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}
 
that i have used for creating the log.
 
I has not been able to show the correct values using log4view.
 
What am i wrong ???
Thanks in advance
Stefano

 

----- Original Message -----

From: Ulrich [via Log4View Support]

Sent: 09/27/13 08:21 AM

To: delfo

Subject: AW: Problem with NLog log

 

Hi Stefano,

 

 

 

 

 

the current version of Log4View only offers log4net keywords.

 

 

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

Ulrich Proeller

 

 

PROSA GmbH

 

 

 

 

 

Greinerstraße 23a

 

 

86316 Friedberg

 

 

Fon: +49 821 45061081

 

 

Fax: +49 821 45061082

 

 

Mobile: +49 170 5417282

 

 

www.prosa-gmbh.de

 

 

[hidden email]

 

 


PROSA Gesellschaft für System und Anwendungsentwicklung mbH

 

 

GF: Ulrich Proeller, Ulrike Proeller

 

 

AG Augsburg, HRB 17165

 

 

Ust.-Id. Nr: DE202375536

 

 

 

 

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Donnerstag, 26. September 2013 21:55
An: Ulrich Proeller
Betreff: Problem with NLog log

 

 

 

 

 

hi,
i have an application that produce a log file similar to this

Debug   10   12472   2013-09-26 21:42:57.1402  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.1582  Program                  It's gonna happen!!:09.42.57.164238
Debug   10   12472   2013-09-26 21:42:57.3652  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.3652  Program                  It's gonna happen!!:09.42.57.365266
Debug   10   12472   2013-09-26 21:42:57.5662  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.5662  Program                  It's gonna happen!!:09.42.57.566289
Debug   10   12472   2013-09-26 21:42:57.7673  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.7673  Program                  It's gonna happen!!:09.42.57.767314
Debug   10   12472   2013-09-26 21:42:57.9683  Program                  We're going to throw an exception now.
Warn    10   12472   2013-09-26 21:42:57.9683  Program                  It's gonna happen!!:09.42.57.968341

using this layout setting
              layout="${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}"

the problem is that when i try to load this file under the Layoutpattern options i cannot reach to find any of NLog keywords even the ComboBox shows 2 NLog entries.
What am i wrong ??
Thanks in advance
Stefano
 

 

 


If you reply to this email, your message will be added to the discussion below:

 

 

http://forum.log4view.com/Problem-with-NLog-log-tp20.html

 

 

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML

 

 

 
If you reply to this email, your message will be added to the discussion below:
http://forum.log4view.com/Problem-with-NLog-log-tp20p21.html
To unsubscribe from Problem with NLog log, click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.
Reply | Threaded
Open this post in threaded view
|

AW: AW: Problem with NLog log

Ulrich
Administrator

Hi Stefano,

 

Log4View cannot read all pattern formatted log files. Pattern formatted log files are intended to be human readable, not machine readable. That’s why we heavily recommend XML formatted log files for use with Log4View.

There is no guarantee that Log4View can parse a pattern formatted log file because they can be ambiguous. In most times, adding a unique separator between the different pattern elements helps Log4View to separate the elements and to parse the log file.

 

Thus, change your pattern string to this:

 

${level:padding=-6} | ${threadid:padding=-4} | ${processid} | ${longdate} | ${logger:shortName=true:padding=-24} | ${message} | ${exception:format=ToString,StackTrace}

 

This should work.

 

Mit freundlichen Grüßen / Yours sincerely

 

Ulrich Proeller

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 10:08
An: Ulrich Proeller
Betreff: Re: AW: Problem with NLog log

 

HI,

thanks for the reply.

This is exactly what i have done without success.

Please try to create a simple text log file with the sample data that i write in previous message and use this string

 

${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}

 

that i have used for creating the log.

 

I has not been able to show the correct values using log4view.

 

What am i wrong ???

Thanks in advance

Stefano

 

----- Original Message -----

From: Ulrich [via Log4View Support]

Sent: 09/27/13 08:21 AM

To: delfo

Subject: AW: Problem with NLog log

 

Hi Stefano,

 

 

 

 

 

the current version of Log4View only offers log4net keywords.

 

 

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

Ulrich Proeller

 

 

PROSA GmbH

 

 

 

 

 

Greinerstraße 23a

 

 

86316 Friedberg

 

 

Fon: +49 821 45061081

 

 

Fax: +49 821 45061082

 

 

Mobile: +49 170 5417282

 

 

click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.


If you reply to this email, your message will be added to the discussion below:

http://forum.log4view.com/Problem-with-NLog-log-tp20p22.html

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support,
click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: AW: AW: Problem with NLog log

delfo
HI,
thanks again for your support and your patience !!!
Create an XML formatted log will be great but i has not been able to find anything in internet about how to do this with NLog.
Could you suggest me or point me to the right direction ????
Thanks again
Stefano

 

----- Original Message -----

From: Ulrich [via Log4View Support]

Sent: 09/27/13 10:20 AM

To: delfo

Subject: AW: AW: Problem with NLog log

 

Hi Stefano,

 

 

 

 

 

Log4View cannot read all pattern formatted log files. Pattern formatted log files are intended to be human readable, not machine readable. That’s why we heavily recommend XML formatted log files for use with Log4View.

 

 

There is no guarantee that Log4View can parse a pattern formatted log file because they can be ambiguous. In most times, adding a unique separator between the different pattern elements helps Log4View to separate the elements and to parse the log file.

 

 

 

 

 

Thus, change your pattern string to this:

 

 

 

 

 

${level:padding=-6} | ${threadid:padding=-4} | ${processid} | ${longdate} | ${logger:shortName=true:padding=-24} | ${message} | ${exception:format=ToString,StackTrace}

 

 

 

 

 

This should work.

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 10:08
An: Ulrich Proeller
Betreff: Re: AW: Problem with NLog log

 

 

 

 

 

HI,

 

 

thanks for the reply.

 

 

This is exactly what i have done without success.

 

 

Please try to create a simple text log file with the sample data that i write in previous message and use this string

 

 

 

 

 

${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}

 

 

 

 

 

that i have used for creating the log.

 

 

 

 

 

I has not been able to show the correct values using log4view.

 

 

 

 

 

What am i wrong ???

 

 

Thanks in advance

 

 

Stefano

 

 

 

 

 

----- Original Message -----

 

 

From: Ulrich [via Log4View Support]

 

 

Sent: 09/27/13 08:21 AM

 

 

To: delfo

 

 

Subject: AW: Problem with NLog log

 

 

 

 

 

Hi Stefano,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the current version of Log4View only offers log4net keywords.

 

 

 

 

 

 

 

 

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

 

 

 

PROSA GmbH

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Greinerstraße 23a

 

 

 

 

 

 

 

 

86316 Friedberg

 

 

 

 

 

 

 

 

Fon: +49 821 45061081

 

 

 

 

 

 

 

 

Fax: +49 821 45061082

 

 

 

 

 

 

 

 

Mobile: +49 170 5417282

 

 

 

 

 

 

 

 

click here.
NAML

 

 

 

 

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.

 

 


If you reply to this email, your message will be added to the discussion below:

 

 

http://forum.log4view.com/Problem-with-NLog-log-tp20p22.html

 

 

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML

 

 

 
If you reply to this email, your message will be added to the discussion below:
http://forum.log4view.com/Problem-with-NLog-log-tp20p23.html
To unsubscribe from Problem with NLog log, click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.
Reply | Threaded
Open this post in threaded view
|

AW: AW: AW: Problem with NLog log

Ulrich
Administrator

Hi Stefano

 

The following XML-fragment configures an XML-file as NLOG target:

      <target name="xmlfile" xsi:type="File" fileName="${basedir}LogEmiter.Nlog.xlog" keepFileOpen="true" 

              layout="${log4jxmlevent:includeCallSite=true:includeMdc=true:appInfo=LogEmiter:includeNdc=true:includeNLogData=true}" />

 

See also: https://github.com/nlog/NLog/wiki/Log4JXMLEvent-Layout-Renderer

 

Mit freundlichen Grüßen / Yours sincerely

 

Ulrich Proeller

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 14:59
An: Ulrich Proeller
Betreff: Re: AW: AW: Problem with NLog log

 

HI,

thanks again for your support and your patience !!!

Create an XML formatted log will be great but i has not been able to find anything in internet about how to do this with NLog.

Could you suggest me or point me to the right direction ????

Thanks again

Stefano

 

----- Original Message -----

From: Ulrich [via Log4View Support]

Sent: 09/27/13 10:20 AM

To: delfo

Subject: AW: AW: Problem with NLog log

 

Hi Stefano,

 

 

 

 

 

Log4View cannot read all pattern formatted log files. Pattern formatted log files are intended to be human readable, not machine readable. That’s why we heavily recommend XML formatted log files for use with Log4View.

 

 

There is no guarantee that Log4View can parse a pattern formatted log file because they can be ambiguous. In most times, adding a unique separator between the different pattern elements helps Log4View to separate the elements and to parse the log file.

 

 

 

 

 

Thus, change your pattern string to this:

 

 

 

 

 

${level:padding=-6} | ${threadid:padding=-4} | ${processid} | ${longdate} | ${logger:shortName=true:padding=-24} | ${message} | ${exception:format=ToString,StackTrace}

 

 

 

 

 

This should work.

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 10:08
An: Ulrich Proeller
Betreff: Re: AW: Problem with NLog log

 

 

 

 

 

HI,

 

 

thanks for the reply.

 

 

This is exactly what i have done without success.

 

 

Please try to create a simple text log file with the sample data that i write in previous message and use this string

 

 

 

 

 

${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}

 

 

 

 

 

that i have used for creating the log.

 

 

 

 

 

I has not been able to show the correct values using log4view.

 

 

 

 

 

What am i wrong ???

 

 

Thanks in advance

 

 

Stefano

 

 

 

 

 

----- Original Message -----

 

 

From: Ulrich [via Log4View Support]

 

 

Sent: 09/27/13 08:21 AM

 

 

To: delfo

 

 

Subject: AW: Problem with NLog log

 

 

 

 

 

Hi Stefano,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the current version of Log4View only offers log4net keywords.

 

 

 

 

 

 

 

 

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

 

 

 

PROSA GmbH

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Greinerstraße 23a

 

 

 

 

 

 

 

 

86316 Friedberg

 

 

 

 

 

 

 

 

Fon: +49 821 45061081

 

 

 

 

 

 

 

 

Fax: +49 821 45061082

 

 

 

 

 

 

 

 

Mobile: +49 170 5417282

 

 

 

 

 

 

 

 

click here.
click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.

 


If you reply to this email, your message will be added to the discussion below:

http://forum.log4view.com/Problem-with-NLog-log-tp20p24.html

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: AW: AW: AW: Problem with NLog log

delfo
Hi,
thanks for the support.
Now all works fine and you logger is very awesome !!!
So i have decide to buy it and i'm wait for the license.
In the meantime can i ask for another question ???
Is your viewer capable of work as a network receiver for NLog ???
 
In my app i would like to use somethings like this :
 
  <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <targets>
      <target 
                 name="network" xsi:type="Network" 
                address="tcp://127.0.0.1:9999" 
                layout="${log4jxmlevent:includeSourceInfo=true:includeCallSite=true:includeMdc=true:appInfo=LogEmiter:includeNdc=true:includeNLogData=true}"
            />
    </targets>
 
    <rules>
      <logger name="*" minlevel="Debug" writeTo="network" />
    </rules>
  </nlog>
 
Thanks again
Stefano
 
 
 
 
 

 

----- Original Message -----

From: Ulrich [via Log4View Support]

Sent: 09/27/13 03:11 PM

To: delfo

Subject: AW: AW: AW: Problem with NLog log

 

Hi Stefano

 

 

 

 

 

The following XML-fragment configures an XML-file as NLOG target:

 

 

      <target name="xmlfile" xsi:type="File" fileName="${basedir}LogEmiter.Nlog.xlog" keepFileOpen="true" 

 

 

              layout="${log4jxmlevent:includeCallSite=true:includeMdc=true:appInfo=LogEmiter:includeNdc=true:includeNLogData=true}" />

 

 

 

 

 

See also: https://github.com/nlog/NLog/wiki/Log4JXMLEvent-Layout-Renderer

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 14:59
An: Ulrich Proeller
Betreff: Re: AW: AW: Problem with NLog log

 

 

 

 

 

HI,

 

 

thanks again for your support and your patience !!!

 

 

Create an XML formatted log will be great but i has not been able to find anything in internet about how to do this with NLog.

 

 

Could you suggest me or point me to the right direction ????

 

 

Thanks again

 

 

Stefano

 

 

 

 

 

----- Original Message -----

 

 

From: Ulrich [via Log4View Support]

 

 

Sent: 09/27/13 10:20 AM

 

 

To: delfo

 

 

Subject: AW: AW: Problem with NLog log

 

 

 

 

 

Hi Stefano,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Log4View cannot read all pattern formatted log files. Pattern formatted log files are intended to be human readable, not machine readable. That’s why we heavily recommend XML formatted log files for use with Log4View.

 

 

 

 

 

 

 

 

There is no guarantee that Log4View can parse a pattern formatted log file because they can be ambiguous. In most times, adding a unique separator between the different pattern elements helps Log4View to separate the elements and to parse the log file.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Thus, change your pattern string to this:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

${level:padding=-6} | ${threadid:padding=-4} | ${processid} | ${longdate} | ${logger:shortName=true:padding=-24} | ${message} | ${exception:format=ToString,StackTrace}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This should work.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Von: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 27. September 2013 10:08
An: Ulrich Proeller
Betreff: Re: AW: Problem with NLog log

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

HI,

 

 

 

 

 

 

 

 

thanks for the reply.

 

 

 

 

 

 

 

 

This is exactly what i have done without success.

 

 

 

 

 

 

 

 

Please try to create a simple text log file with the sample data that i write in previous message and use this string

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

${level:padding=-6}  ${threadid:padding=-4} ${processid}   ${longdate}  ${logger:shortName=true:padding=-24} ${message} ${exception:format=ToString,StackTrace}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

that i have used for creating the log.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

I has not been able to show the correct values using log4view.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

What am i wrong ???

 

 

 

 

 

 

 

 

Thanks in advance

 

 

 

 

 

 

 

 

Stefano

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

----- Original Message -----

 

 

 

 

 

 

 

 

From: Ulrich [via Log4View Support]

 

 

 

 

 

 

 

 

Sent: 09/27/13 08:21 AM

 

 

 

 

 

 

 

 

To: delfo

 

 

 

 

 

 

 

 

Subject: AW: Problem with NLog log

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hi Stefano,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the current version of Log4View only offers log4net keywords.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To read NLog generated log files, just paste your NLog format string into the appropriate field in Log4view.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Mit freundlichen Grüßen / Yours sincerely

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ulrich Proeller

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PROSA GmbH

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Greinerstraße 23a

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

86316 Friedberg

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Fon: +49 821 45061081

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Fax: +49 821 45061082

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Mobile: +49 170 5417282

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

click here.
click here.
NAML

 

 

 

 

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.

 

 

 

 

 


If you reply to this email, your message will be added to the discussion below:

 

 

http://forum.log4view.com/Problem-with-NLog-log-tp20p24.html

 

 

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML

 

 

 
If you reply to this email, your message will be added to the discussion below:
http://forum.log4view.com/Problem-with-NLog-log-tp20p25.html
To unsubscribe from Problem with NLog log, click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.
Reply | Threaded
Open this post in threaded view
|

RE: AW: AW: AW: Problem with NLog log

Ulrich
Administrator

Attached, you find a config file with a bunch of different configurations for NLog and for log4net.

There is a log target called „network“ which configures a NLog network target, which can be read by Log4View.

 

Mit freundlichen Grüßen / Yours sincerely

 

Ulrich Proeller

 

From: delfo [via Log4View Support] [mailto:ml-node+[hidden email]]
Sent: Saturday, September 28, 2013 6:41 AM
To: Ulrich Proeller
Subject: Re: AW: AW: AW: Problem with NLog log

 

Hi,

thanks for the support.

Now all works fine and you logger is very awesome !!!

So i have decide to buy it and i'm wait for the license.

In the meantime can i ask for another question ???

Is your viewer capable of work as a network receiver for NLog ???

 

In my app i would like to use somethings like this :

 

  <nlog xmlns="" target="_top" rel="nofollow" link="external">click here.
NAML

 




_________________
AVVISO DI RISERVATEZZA Le informazioni trasmesse sono da intendere solo per la persona o ente a cui sono indirizzate, possono contenere documenti confidenziali e materiale riservato. Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte di persone o enti, diversi dai destinatari indicati, è proibito ai sensi del D.Lg. n. 196 del 30/06/2003. Qualora fosse da Voi ricevuto per errore vogliate cortesemente rinviarlo al mittente e cancellare queste informazioni da ogni computer. Grazie per la collaborazione.

CONFIDENTIALITY NOTICE The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and previleged material. Any review, trasmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited (italian law D.Lg. n. 196, 30/06/2003). If you are not the intended recipient, please contact the sender and delete the mail from any computer. Thank you for your cooperation.

 


If you reply to this email, your message will be added to the discussion below:

http://forum.log4view.com/Problem-with-NLog-log-tp20p26.html

To start a new topic under Log4View Support, email [hidden email]
To unsubscribe from Log4View Support, click here.
NAML


App.config (39K) Download Attachment