Comments (5)
Have you created the index pattern in Kibana? The pattern to use is "logstash-pfsense-*". If so, do the src_ip.keyword and dest_port.keyword fields exist for the mapping?
from logstash-pfsense.
I had already created the index pattern logstash-pfsense-* but when I look in the fields, it doesn't hve src_ip.keyword or dest_port.keyword. Do I have to create these fields manually on the index pattern? Sorry I'm not very familiar with it, so would really appreciate some help.
from logstash-pfsense.
Ok - when I deleted the index and re-created it after I had imported the visualizations in Kibana, it created the index with additional fields, which included src_ip.keyword and dest_port.keyword. And the visualizations and dashboard work now.
So do I have to import the visualization first, so Kibana knows about the additional fields that the index requires? Before creating the index?
from logstash-pfsense.
The simplest steps would be to setup pfsense and logstash first and have events flow naturally into elasticsearch. This will create the index and fields automatically as they are inserted. It seems in your instance, the events that were pushed through the stack did not contain src_ip and dest_port data. Maybe pfsense was not pushing firewall events and only other syslog data at the time? Anyway, when you initially created the index pattern in kibana, it did not pick up those fields because they did not exist on the index.
Refreshing the index pattern fields in kibana is the correct solution. There is a refresh fields button in kibana that you can press at anytime to pick up any missing fields for the pattern.
from logstash-pfsense.
I have the same issue. Are you available to reproduce and check?
May it be due to different log format from pfsense ?
from logstash-pfsense.
Related Issues (10)
- PFSENSE_LOG_DATA doesn't match vlan interfaces HOT 1
- Issue with [prog] regex in 11-pfsense.conf HOT 1
- Pattern %{PFSENSE_LOG_DATA} not defined HOT 2
- _grokparsefailure on some lines HOT 4
- Merge with opnsense-logstash-config HOT 1
- license?
- Not populating all values for tcp_flags HOT 5
- Problem : Cannot create pipeline {:reason=>"Expected one of #, } at line 122, column 22 (byte 2959) after output {\n if [type] == \"syslog\" {\n elasticsearch {\n hosts => 10.1"}
- Filterlog not begining the string for |prog]
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from logstash-pfsense.