# MOnitoring mysql & http traffic in Packetbeat dashboards

**URL:** <https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [May 18, 2017, 4:08pm UTC](https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305 "2017-05-18T16:08:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JayArthur](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@JayArthur](https://discuss.elastic.co/u/JayArthur)\
**Post date:** [May 18, 2017, 4:08pm UTC](https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305/1 "2017-05-18T16:08:03Z")

</div>

Hey guys, I cannot seem to monitor MySQL and http traffic using packetbeat dashboards despite opening the ports on client machines. someone kindly advise me on what to do.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 18, 2017, 4:56pm UTC](https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305/2 "2017-05-18T16:56:09Z")

</div>

Can you share your Packetbeat config and logs? Where is Packetbeat running? On a machine that makes mysql and http requests? Or is it on the myqsl or http server?

---

<div class="post-metadata">

**Author:** ![JayArthur](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@JayArthur](https://discuss.elastic.co/u/JayArthur)\
**Post date:** [May 19, 2017, 6:54am UTC](https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305/3 "2017-05-19T06:54:14Z")

</div>

Sure, here's my packetbeat configuration

#################### Packetbeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common

# options. The packetbeat.full.yml file from the same directory contains all the

# supported options with more comments. You can use it as a reference.

# 

# You can find the full configuration reference here:

# [https://www.elastic.co/guide/en/beats/packetbeat/index.html](https://www.elastic.co/guide/en/beats/packetbeat/index.html)

#============================== Network device ================================

# Select the network interface to sniff the data. On Linux, you can use the

# "any" keyword to sniff on all connected interfaces.

packetbeat.interfaces.device: any

#================================== Flows =====================================

# Set `enabled: false` or comment out all options to disable flows reporting.

packetbeat.flows:

# Set network flow timeout. Flow is killed if no packet is received before being

# timed out.

timeout: 30s

# Configure reporting period. If set to -1, only killed flows will be reported

period: 10s

#========================== Transaction protocols =============================

packetbeat.protocols.icmp:

# Enable ICMPv4 and ICMPv6 monitoring. Default: false

enabled: true

packetbeat.protocols.amqp:

# Configure the ports where to listen for AMQP traffic. You can disable

# the AMQP protocol by commenting out the list of ports.

ports: [5672]

packetbeat.protocols.cassandra:  
#Cassandra port for traffic monitoring.  
ports: [9042]

packetbeat.protocols.dns:

# Configure the ports where to listen for DNS traffic. You can disable

# the DNS protocol by commenting out the list of ports.

ports: [53]

# include\_authorities controls whether or not the dns.authorities field

# (authority resource records) is added to messages.

include\_authorities: true

# include\_additionals controls whether or not the dns.additionals field

# (additional resource records) is added to messages.

include\_additionals: true

packetbeat.protocols.http:

# Configure the ports where to listen for HTTP traffic. You can disable

# the HTTP protocol by commenting out the list of ports.

ports: [80, 8080, 8000, 5000, 8002]

packetbeat.protocols.memcache:

# Configure the ports where to listen for memcache traffic. You can disable

# the Memcache protocol by commenting out the list of ports.

ports: [11211]

packetbeat.protocols.mysql:

# Configure the ports where to listen for MySQL traffic. You can disable

# the MySQL protocol by commenting out the list of ports.

ports: [3306]

packetbeat.protocols.pgsql:

# Configure the ports where to listen for Pgsql traffic. You can disable

# the Pgsql protocol by commenting out the list of ports.

ports: [5432]

packetbeat.protocols.redis:

# Configure the ports where to listen for Redis traffic. You can disable

# the Redis protocol by commenting out the list of ports.

ports: [6379]

packetbeat.protocols.thrift:

# Configure the ports where to listen for Thrift-RPC traffic. You can disable

# the Thrift-RPC protocol by commenting out the list of ports.

ports: [9090]

packetbeat.protocols.mongodb:

# Configure the ports where to listen for MongoDB traffic. You can disable

# the MongoDB protocol by commenting out the list of ports.

ports: [27017]

packetbeat.protocols.nfs:

# Configure the ports where to listen for NFS traffic. You can disable

# the NFS protocol by commenting out the list of ports.

ports: [2049]

#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group

# all the transactions sent by a single shipper in the web interface.

#name:

# The tags of the shipper are included in their own field with each

# transaction published.

#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the

# output.

#fields:

# env: staging

#================================ Outputs =====================================

# Configure what outputs to use when sending the data collected by the beat.

# Multiple outputs may be used.

#-------------------------- Elasticsearch output ------------------------------  
#output.elasticsearch:

# Array of hosts to connect to.

# hosts: ["localhost:9200"]

# Optional protocol and basic auth credentials.

#protocol: "https"  
#username: "elastic"  
#password: "changeme"

#----------------------------- Logstash output --------------------------------  
output.logstash:

# The Logstash hosts

hosts: ["10.200.21.32:5044"]

# Optional SSL. By default is off.

# List of root certificates for HTTPS server verifications

ssl.certificate\_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"]

# Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

# Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

#================================ Logging =====================================

# Sets log level. The default log level is info.

# Available log levels are: critical, error, warning, info, debug

#logging.level: debug

# At debug level, you can selectively enable logging only for some components.

# To enable all selectors use ["\*"]. Examples of other selectors are "beat",

# "publish", "service".

#logging.selectors: ["\*"]

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 16, 2017, 6:54am UTC](https://discuss.elastic.co/t/monitoring-mysql-http-traffic-in-packetbeat-dashboards/86305/4 "2017-06-16T06:54:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.