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

Make the bluecoat sourcetype match the sourcetype defined in the Splunk bluecoat addon #2347

Closed
myriadic opened this issue Feb 15, 2024 · 2 comments
Assignees

Comments

@myriadic
Copy link

What is the sc4s version ?
most recent

Is there a pcap available?
no

What the vendor name?
Symantec

What's the product name?
BluecoatProxy

** Feature Request description: **
Make the bluecoat sourcetype match the sourcetype defined in the Splunk bluecoat addon

** Should it support TCP or UDP?**
UDP

** Do you want to have it for local usage or prepare a github PR? **
github PR

The Bluecoat addon has "KV_MODE = none" for the bluecoat sourcetype, which means the field extractions will have to match the SC4S format.

The issue with this is that SC4S strips out the timestamp. For the field extractions to work, even after making the sourcetypes match, the timestamps in the bluecoat addon need to be marked as optional in the field extraction REGEX

@mstopa-splunk
Copy link
Contributor

Hi @myriadic thanks for catching this.

sourcetype fix should be merged in one of the next releases: #2370
In the meantime I will pass the info about incorrect REGEX to the addon owners. Can you send me an example of the event to test? The one we have in repo is not super useful for this.

@mstopa-splunk
Copy link
Contributor

sourcetype fix released in v3.25.0, regex needs to be fixed on the add-on side, please send a few samples to mstopa@splunk.com or to Splunk support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants