Packetbeat building to v7

(Manthan Sharma) #1


I am building packetbeat, using the master branch, It's building successfully, but after checking the version of binary, it's showing it to be v7.0.0.

packetbeat version 7.0.0-alpha1 (amd64), libbeat 7.0.0-alpha1 [9bf3c2f1267a0c1ebdeb50504ce69cacd197a937 built 2018-02-26 01:12:10 +0000 UTC]

And using this binary to setup Kibana dashboard, causing dashboard to produce errors,


(Steffen Siering) #2

Master branch is basically the development branch. As the next major release will be v7, the master branch reports itself as v7 for now.

Which kibana version are you using? Have you tested with most recent 6.2 release?

(Axrayn) #3

I had the same problem with Packetbeat 6.2.1 from the yum repo.

I solved it by updating the visualisations to use the .keyword versions of any string fields it was trying to access.

(Manthan Sharma) #4

ElasticSearch: Version: 6.2.1, Build: 7299dc3/2018-02-07T19:34:26.990113Z, JVM: 1.8.0_111
Kibana: 6.2.2
Packetbeat: Maste Branch, Last Commit Hash: 911a1ab26dd8cc64ec4fb1f3fa228512066a3ef2,

This is my ElasticStack I am using for development.

(ruflin) #5

I haven't tested recently packetbeat master with a stable release of Kibana. In general we try to keep compatibility which does not seem to be the case here. Could you open a Github issue with this so we can investigate on why this error happens?

It would be interesting to know if you see the error also when running Packetbeat master against Kibana master.

(system) #6

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