Unfortunately you'd have to use another IP source in order to apply haproxy:tcp due to the fact it is impossible to define two different source types under the same IP source. If you can somehow transfer your tcp logs to a different port (for example 8514 instead of 514) that would do, then you could use [udp://192.168.1.1:514] connection_host = ip sourcetype = haproxy:http [udp://192.168.1.1:8514] connection_host = ip sourcetype = haproxy:tcp and there wouldn't be an error. This is a workaround though, maybe someone else could find an easier solution. ... View more

You can't use the same header twice in inputs.conf, therefore the TCP logs don't match the TCP sourcetype. you need to define two listeners in haproxy.cfg and only use one sourcetype per header in inputs.conf . Duplication of a header (in your case [udp://192.168.1.1:514]) is a syntax error and the parser disregards the second. ... View more

Try to create a new listener for the TCP format to the same device, this way you could have two different source types for the same device. Since the listeners are independent that should work. Here is an example for using two listeners for the same servers (in this case both use mode tcp, but you can alter one of them to mode http): listen haproxy_192.168.55.110_3307_multi bind *:3307 mode tcp timeout client 10800s timeout server 10800s balance leastconn option httpchk option allbackups default-server port 9200 inter 2s downinter 5s rise 3 fall 2 slowstart 60s maxconn 64 maxqueue 128 weight 100 server galera1 192.168.55.111:3306 check server galera2 192.168.55.112:3306 check server galera3 192.168.55.113:3306 check listen haproxy_192.168.55.110_3308_single bind *:3308 mode tcp timeout client 10800s timeout server 10800s balance leastconn option httpchk option allbackups default-server port 9200 inter 2s downinter 5s rise 3 fall 2 slowstart 60s maxconn 64 maxqueue 128 weight 100 server galera1 192.168.55.111:3306 check server galera2 192.168.55.112:3306 check backup server galera3 192.168.55.113:3306 check backup Taken from https://severalnines.com/resources/tutorials/mysql-load-balancing-haproxy-tutorial Test that and see if it can solve this problem. ... View more

Your second query seems wrong, the text inputs if they don't contain query conditions are errors (also, this is not a dynamic query, so it just seems wrong) try the following query instead: | dbxquery="SELECT * FROM table WHERE (Event_Date BETWEEN '2017-05-01 00:00:00.0' AND '2017-05-30 23:59:59.0')" connection="connection_name" wrap=t If you want to use text inputs instead of the dates you can do the following (assuming $dateok1$ = '2017-05-01 00:00:00.0' and $dateok2$ = '2017-05-30 23:59:59.0'): | dbxquery="SELECT * FROM table WHERE (Event_Date BETWEEN $dateok1$ AND $dateok2$)" connection="connection_name" wrap=t or as you tried at first | dbxquery query="SELECT * FROM table WHERE (Event_Date>$dateok1$ AND Event_Date<$dateok2$)" connection="connection_name" wrap=t I recommend the first option I mentioned (The BETWEEN method is more efficient) but all three should work. ... View more

If you're using MySQL this could help: Condition or Error When using DirectReads, the connector reports errors with a broken pipe. Causes The most likely culprit for this error is that the wait_timeout and/or interactive_timeout is too low. This causes a problem because pooled connections get timeouts and are closed by the MySQL server. Rectifications Change the configuration for your MySQL server (in my.cnf) to increase these timeouts. If you're using another database server please add that information and I'll try to help (I assumed MySQL because broken pipes are more common in them).,In case you're using a MySQL server this could work: Condition or Error When using DirectReads, the connector reports errors with a broken pipe. Causes The most likely culprit for this error is that the wait_timeout and/or interactive_timeout is too low. This causes a problem because pooled connections get timeouts and are closed by the MySQL server. Rectifications Change the configuration for your MySQL server (in my.cnf) to increase these timeouts. If you're using another database server please mention which type and I'll try to help. ... View more