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

Splunk Mapping reverts to default source of WinEventLog regardless of RootA configuration #146

Open
britton-from-notion opened this issue Jun 13, 2024 · 1 comment

Comments

@britton-from-notion
Copy link

Hey there!

It looks like the uncoder RootA to Splunk translator does not reflect provided index and source type information from an SPL query. It reverts to a windows event log as a source despite windows event log not being present in my RootA configuration.

My guess is it’s happening somewhere around here and is related to the source mapping functionality.

Let me know if you've got any ideas on why this might be happening or how I could solve it! Thank you!

IMG_3618

@Ginger-Headed
Copy link
Collaborator

Hi!

Log sources are defined by source and sourcetype field values. It is not based on an index name since the index name can be custom and not explicitly related to the log source.

Section default_log_source in the mapping field defines the log source for the render (destination query). However, we found another issue: it is not working correctly for some log sources. We will work on the fix.

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