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 are my hero. now I need need to go back and update about 20 inefficient dashboards I have made over time knowing that this should have been a thing all along. #SmartAnswers ... View more

Hi Azamir! MSSQL Server 2016 is the backend for our SCCM instance. I thought I had put that in there, but apparently not. I will edit for clarity. Also, it didn't appear to me that pooled connections would be the issue since we are able to get data back using "| dbxquery", but I will look into it. Thanks for the info! ... View more