{"id":273,"date":"2016-03-30T12:55:10","date_gmt":"2016-03-30T10:55:10","guid":{"rendered":"http:\/\/blogs.msdn.microsoft.com\/lavanack\/?p=273"},"modified":"2022-05-30T13:50:04","modified_gmt":"2022-05-30T11:50:04","slug":"logparser-your-best-friend","status":"publish","type":"post","link":"https:\/\/laurentvanacker.com\/index.php\/2016\/03\/30\/logparser-your-best-friend\/","title":{"rendered":"Besoin d’analyser vos logs IIS ? LogParser est votre meilleur ami ! \/ Need to analyse your IIS log files? LogParser is your best friend !"},"content":{"rendered":"
English version<\/a><\/div>\n

[MAJ 01\/03\/2017] Est-il encore besoin de pr\u00e9senter LogParser<\/a> ? Cet outil en ligne de commandes est un veritable couteau suisse et permet d’analyser une multitude de formats de fichier (Log IIS, fichier XML, Traces venant de Network Monitor, Traces ETW, …). Certes il existe d’excellents outils tel que LogParserStudio<\/a> auquel mes coll\u00e8gues de l’\u00e9quipe support IIS\/Azure France ont m\u00eame consacr\u00e9 un article<\/a> mais il faut l’avouer je suis assez \u00ab\u00a0old school\u00a0\u00bb et je pr\u00e9f\u00e9re directement utiliser l’outil de base plut\u00f4t qu’une surcouche (m\u00eame si je le r\u00e9p\u00e8te l’outil semble tr\u00e8s bien fait).<\/p>\n

Dans le cadre d’une analyse des logs IIS le temps consacr\u00e9 pour se familiariser avec LogParser (j’estime \u00e0 moins de 4 heures en partant de z\u00e9ro) me semble d\u00e9risoire par rapport au retour sur investissement lors de vos phases de troubleshooting. De mani\u00e8re \u00e0 encore acc\u00e9lerer votre apprentissage, j’ai d\u00e9cid\u00e9 de vous livrer les requ\u00eates LogParser que j’utilise le plus fr\u00e9quement lors de mes visites clients d\u00e9di\u00e9es \u00e0 des probl\u00e9matiques IIS. Pour cela vous aurez besoin de LogParser 2.2<\/a> et de Office 2003 Add-in: Office Web Components<\/a> (Et oui on va g\u00e9n\u00e9rer des graphiques avec LogParser !). Je recommande d’ailleur d’installer LogParser 2.2<\/a> sur tous vos serveurs IIS de mani\u00e8re \u00e0 pouvoir sortir rapidement un \u00e9tat des lieux des requ\u00eates en cas de probl\u00e8me. Pour Office 2003 Add-in: Office Web Components<\/a>\u00a0 par contre, installez le uniquement sur votre poste de travail (sans oublier LogParser 2.2<\/a>) car il est pr\u00e9f\u00e9rable de g\u00e9nerer vos graphiques sur votre poste de travail et d’installer le minimum de composants sur un serveur de production.<\/p>\n

Nous supposerons pour des facilit\u00e9s de lecture que Logparser.exe est accessible depuis n’importe o\u00f9 (ie. le chemin d’installation est pr\u00e9sent dans votre variable d’environnement PATH)<\/p>\n

<\/div>\n

Le fichier LogParserScript.js<\/a> r\u00e9f\u00e9renc\u00e9 dans quelques lignes qui pr\u00e9c\u00e9dent est disponible ici<\/a> (ne sert que pour les graphiques)<\/p>\n

Toutes les requ\u00eates peuvent \u00eatre t\u00e9l\u00e9charg\u00e9es ici<\/a>.<\/p>\n

\n
Version fran\u00e7aise<\/a><\/div>\n

[Updated 03\/01\/2017] Does it still need to present LogParser<\/a>? This command line tool is a real Swiss Army knife and analyzes a multitude of file formats (IIS Log files, XML files, Network Monitor traces, ETW traces, …). There are excellent tools such as LogParserStudio<\/a> for which my colleagues in the French IIS\/Azure Support Team have even devoted an article<\/a> but I must admit I’m pretty \u00ab\u00a0old school\u00a0\u00bb and I prefer use directly this tool rather than an wrapper (although I repeat the tool seems very well done).<\/p>\n

As part of an IIS logs analysis the time spent to learn LogParser (I estimate at less than 4 hours from scratch) seems paltry compared to the return on investment when you will troubleshoot your IIS servers. <\/span>In order to further accelerate your learning, I have decided to give you the LogParser queries that I use most often during my customer onsites related to IIS issues. <\/span>For this you will need LogParser 2.2<\/a> and Office 2003 Add-in: Office Web Components<\/a> (And yes we will generate graphs with LogParser!). <\/span>BTW I recommend installing LogParser 2.2<\/a><\/span> on all of your IIS servers so you can quickly generate an IIS report of the requests in case of problems. For <\/span>Office 2003 Add-in: Office Web Components<\/a><\/span> I recommend to install only on your computer (don’t forget to install also LogParser 2.2<\/a><\/span>) because it is preferable to generate your charts on your desktop and install the minimum components on a <\/span>production server.<\/span><\/p>\n

We assume to facilitate the reading that LogParser.exe is accessible from anywhere (ie. The installation path is in your PATH environment variable)<\/p>\n

<\/div>\n

The file LogParserScript.js<\/a> (used in some lines above) is available here<\/a> (only used for the chart generation)<\/p>\n

All the requests can be downloaded here<\/a>.<\/p>\n

Laurent.<\/p>\n","protected":false},"excerpt":{"rendered":"

English version [MAJ 01\/03\/2017] Est-il encore besoin de pr\u00e9senter LogParser ? Cet outil en ligne de commandes est un veritable couteau suisse et permet d’analyser […]<\/p>\n","protected":false},"author":2,"featured_media":2465,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,18],"tags":[25,55,30],"class_list":["post-273","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iis","category-ms-dos","tag-iis","tag-logparser","tag-ms-dos"],"_links":{"self":[{"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/posts\/273","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/comments?post=273"}],"version-history":[{"count":8,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/posts\/273\/revisions"}],"predecessor-version":[{"id":2926,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/posts\/273\/revisions\/2926"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/media\/2465"}],"wp:attachment":[{"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/media?parent=273"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/categories?post=273"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/laurentvanacker.com\/index.php\/wp-json\/wp\/v2\/tags?post=273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}