Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packetbeat misconfigured default JSON setting #2177

Closed
CrispySteak opened this issue Aug 4, 2016 · 1 comment
Closed

Packetbeat misconfigured default JSON setting #2177

CrispySteak opened this issue Aug 4, 2016 · 1 comment

Comments

@CrispySteak
Copy link

Using Kibana 5.0 v4 on Linux x64 the following fields import as strings rather than numbers (which is more than rather inconvenient and intuitive):

source.stats.net_packets_total
source.stats.net_bytes_total
dest.stats.net_bytes_total
dest.stats.net_packets_total

Problem should be in the beats/packetbeat/etc/kibana/index-pattern/packetbeat.json

Thanks!

@andrewkroh
Copy link
Member

It looks like these fields are marked as keyword type in the index template so both the fields.yml and the dashboards will need to be updated.

andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 9, 2016
The following fields were marked as not_analyzed strings and should be longs.

- source.stats.net_packets_total
- source.stats.net_bytes_total
- dest.stats.net_bytes_total
- dest.stats.net_packets_total

Issue elastic#2177
tsg pushed a commit that referenced this issue Aug 10, 2016
The following fields were marked as not_analyzed strings and should be longs.

- source.stats.net_packets_total
- source.stats.net_bytes_total
- dest.stats.net_bytes_total
- dest.stats.net_packets_total

Issue #2177
@tsg tsg closed this as completed Aug 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants