DOCS-533 - Network sensor end-of-life #5309
Open
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
jpipkin1
added
doc:update
jpipkin1
requested review from
kimsauce,
JV0812,
mafsumo and
amee-sumo
as code owners
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
kimsauce
reviewed
Apr 25, 2025
|
|
||
| This configuration step is required to ensure that Cloud SIEM knows how to parse incoming Zeek logs, correctly map the log fields to schema attributes, and create Cloud SIEM records. The most important bit of information is what type of data a particular log contains. Zeek has a variety of log types, for example `conn` for TCP/UDP/ICMP connections, `http` for HTTP requests and replies, and `ftp` for FTP activity. | ||
|
|
||
| So, how to determine whether a Zeek log is a `conn`, `http`, `ftp`, or some other log type? Zeek logs don’t contain a key that explicitly holds a value that is only the log type identifier. There are two options for dealing with this: |
There was a problem hiding this comment.
per https://help.sumologic.com/docs/contributing/style-guide/#contractions
Suggested change
| So, how to determine whether a Zeek log is a `conn`, `http`, `ftp`, or some other log type? Zeek logs don’t contain a key that explicitly holds a value that is only the log type identifier. There are two options for dealing with this: | |
| So, how to determine whether a Zeek log is a `conn`, `http`, `ftp`, or some other log type? Zeek logs do not contain a key that explicitly holds a value that is only the log type identifier. There are two options for dealing with this: |
kimsauce
reviewed
Apr 25, 2025
| "/Cloud_SIEM_Enterprise/CSE_Sensors/09_Windows_Sensor_Troubleshooting": "/docs/cse/ingestion/ingestion-sources-for-cloud-siem/corelight-zeek", | ||
| "/Cloud_SIEM_Enterprise/CSE_Sensors/13_Network_Sensor_Troubleshooting": "/docs/cse/ingestion/ingestion-sources-for-cloud-siem/corelight-zeek", | ||
| "/Cloud_SIEM_Enterprise/CSE_Sensors/17_Log_Sensor_Troubleshooting": "/docs/cse/ingestion/ingestion-sources-for-cloud-siem/corelight-zeek", | ||
| "/Cloud_SIEM_Enterprise/CSE_Sensors/Ingest_Zeek_Logs": "/docs/cse/ingestion/ingestion-sources-for-cloud-siem/corelight-zeek", |
There was a problem hiding this comment.
Above, are the legacy --> new Docusaurus URL redirects, but you'll also need to add redirects from the old Docusaurus URL to new Docusaurus URL. For example...
"/docs/cse/sensors": "/docs/cse/ingestion/ingestion-sources-for-cloud-siem/corelight-zeek",
kimsauce
requested changes
Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose of this pull request
This pull request:
Select the type of change
Ticket (if applicable)
DOCS-533