# Comment parser les logs de HaProxy **URL:** \ **Category:** Discussions en français\ **Created:** [December 4, 2018, 9:26am UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318 "2018-12-04T09:26:49Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Momo](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@Momo](https://discuss.elastic.co/u/Momo)\ **Post date:** [December 4, 2018, 9:26am UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/1 "2018-12-04T09:26:49Z")
Bonjour, Je débute sur la stack elastic et j'aimerai parser des logs de HaProxy. exemple : ```auto Dec 4 09:09:51 f6047fe55160 local0.info haproxy[1]: 10.255.0.2:11323 [04/Dec/2018:09:09:51.199] http http.actuators.css-1/http.actuators.css-1.1 0/0/1/12/14 200 664 - - ---- 406/11/0/0/0 0/0 "GET /node-1/css/health HTTP/1.1" ``` J'ai testé plusieurs patterns mais en vain. Merci par avance. ---
**Author:** ![MikaMinn](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@MikaMinn](https://discuss.elastic.co/u/MikaMinn)\ **Post date:** [December 4, 2018, 12:14pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/2 "2018-12-04T12:14:36Z")
Bonjour, Je débute également dans le parsing. Si tu ne trouves pas de pattern pré configuré il y a cet outil -\> [Grok Constructor](http://grokconstructor.appspot.com/do/construction) Il m'a permis de bien comprendre le fonctionnement. Et je me suis également renseigné sur les expressions régulières pour paufiner le parsing. ---
**Author:** ![Momo](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@Momo](https://discuss.elastic.co/u/Momo)\ **Post date:** [December 4, 2018, 1:06pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/3 "2018-12-04T13:06:00Z")
Bonjour, Je connais ce site mais merci quand même 🙂 Dans la version 6.5 de kibana tu as aussi un Grok Debugger dans l'onglet Dev Tools. En fait comme HaProxy est load balancing trés connu, je me suis dis qu'il doit exister un pattern. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 4, 2018, 1:07pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/4 "2018-12-04T13:07:39Z")
Genre: [https://github.com/logstash-plugins/logstash-patterns-core/blob/master/patterns/haproxy](https://github.com/logstash-plugins/logstash-patterns-core/blob/master/patterns/haproxy) ? Aussi ceci: [Need help in creating grok patterns for haproxy logs](https://discuss.elastic.co/t/need-help-in-creating-grok-patterns-for-haproxy-logs/134180/8) ---
**Author:** ![MikaMinn](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@MikaMinn](https://discuss.elastic.co/u/MikaMinn)\ **Post date:** [December 4, 2018, 1:16pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/5 "2018-12-04T13:16:42Z")
> [@Momo](#): > > Dans la version 6.5 de kibana tu as aussi un Grok Debugger dans l'onglet Dev Tools. Oui 🙂 mais là c'est la fonctionnalité du "builder" qui est intéressante 😄 ---
**Author:** ![Momo](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@Momo](https://discuss.elastic.co/u/Momo)\ **Post date:** [December 4, 2018, 1:23pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/6 "2018-12-04T13:23:51Z")
J'ai testé les patterns du premier lien mais ça ne match pas mais je vais prendre comme base et essayer d'adapter. Merci. ---
**Author:** ![Momo](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@Momo](https://discuss.elastic.co/u/Momo)\ **Post date:** [December 4, 2018, 1:28pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/7 "2018-12-04T13:28:42Z")
Tu as raison. ---
**Author:** ![Momo](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@Momo](https://discuss.elastic.co/u/Momo)\ **Post date:** [December 4, 2018, 4:38pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/8 "2018-12-04T16:38:08Z")
Voici ma solution : ```auto %{SYSLOGTIMESTAMP:timestamp} %{DATA:Aloha_name} %{DATA:SyslogFacility} %{DATA:Haproxy_process}: %{DATA:client_ip}:%{INT:client_port} \[%{HAPROXYDATE:accept_date}\] %{NOTSPACE:frontend_name} %{NOTSPACE:backend_name}/%{NOTSPACE:server_name} %{INT:Tq}/%{INT:Tw}/%{INT:Tc}/%{INT:Tr}/%{INT:Tt} %{INT:http_status_code} %{NOTSPACE:bytes_read} - - ---- %{INT:actconn}/%{INT:feconn}/%{INT:beconn}/%{INT:srvconn}/%{NOTSPACE:retries} %{INT:srv_queue}/%{INT:backend_queue} "%{WORD:Method} %{URIPATHPARAM:request} HTTP/%{NUMBER:http_version}" ``` [https://cdn.haproxy.com/wp-content/uploads/2017/07/aloha\_load\_balancer\_memo\_log.pdf](https://cdn.haproxy.com/wp-content/uploads/2017/07/aloha_load_balancer_memo_log.pdf) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 1, 2019, 4:43pm UTC](https://discuss.elastic.co/t/comment-parser-les-logs-de-haproxy/159318/9 "2019-01-01T16:43:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.