# Monitoring ES queries from Transport clients? **URL:** \ **Category:** Beats\ **Tags:** packetbeat\ **Created:** [September 12, 2016, 1:50pm UTC](https://discuss.elastic.co/t/monitoring-es-queries-from-transport-clients/60298 "2016-09-12T13:50:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![CliveL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clivel/32/14468_2.png) [@CliveL](https://discuss.elastic.co/u/CliveL)\ **Post date:** [September 12, 2016, 1:50pm UTC](https://discuss.elastic.co/t/monitoring-es-queries-from-transport-clients/60298/1 "2016-09-12T13:50:11Z")
Hi all, I think I already know the answer to this one, but I wanted to check if it is possible to use Packetbeat to monitor ES queries being made to an ES 1.7 cluster from Transport clients (Java API servers) ? They are using the default port of 9300. I haven't had any luck testing with Packetbeat's HTTP monitor on port 9300, and Console output. But a basic HTTP query to port 9200 on the ES 1.7 cluster node does produce Packetbeat pretty JSON output, hence why I think this might be a non-starter... Thanks! ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [September 12, 2016, 2:17pm UTC](https://discuss.elastic.co/t/monitoring-es-queries-from-transport-clients/60298/2 "2016-09-12T14:17:06Z")
The transport protocol is different from the HTTP protocol. That's why it can not be monitored by packetbeat. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 3, 2016, 1:50pm UTC](https://discuss.elastic.co/t/monitoring-es-queries-from-transport-clients/60298/3 "2016-10-03T13:50:33Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.