[pfsense] update pfsense docs #15969
Open
+377
−221
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vinit-chauhan
added
documentation
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
mjwolf
reviewed
Nov 13, 2025
Contributor
mjwolf
left a comment
mjwolf
left a comment
There was a problem hiding this comment.
Could you add a service_info file for this as well?
| # pfSense Integration for Elastic | ||
|
|
||
| ## Overview | ||
| The pfSense integration for Elastic enables the collection of logs from pfSense and OPNsense firewalls. It parses logs received over the network via syslog (UDP, TCP, or TLS), providing visibility into network traffic, security events, and system health. |
Contributor
There was a problem hiding this comment.
(UDP, TCP, or TLS) - TLS isn't a transport, this should probably change to (UDP or TCP) or UDP or TCP, using TLS
| 1. On a host connected to the pfSense network, generate traffic that will trigger a firewall log event. For example, attempt a connection that you know will be blocked by a firewall rule. | ||
| 2. Check the pfSense system logs to confirm that new event data is being written. In the pfSense web interface, navigate to **Status > System Logs > Firewall**. | ||
| 3. In Kibana, navigate to the **Discover** tab or open the pre-built **Firewall - Dashboard [pfSense]** dashboard. | ||
| 4. Filter for pfSense data by using the KQL query `event.dataset : "pfsense.log"`. |
Contributor
There was a problem hiding this comment.
This could be a bit confusing, you don't need to filter, if you choose to open the dashboard
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Update readme for PfSense
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots