We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the sc4s version ? 3.22.5
Which operating system (including its version) are you using for hosting SC4S? does not matter
Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S? does not matter
Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support? does not matter
Is the issue related to the environment of the customer or Software related issue? no
Is it related to Data loss, please explain ? Protocol? Hardware specs? no
Last chance index/Fallback index? no
Is the issue related to local customization? no
Do we have all the default indexes created? does not matter
Describe the bug Current state:
The text was updated successfully, but these errors were encountered:
Hey @ehlo550 Thanks for pointing it out, we will update the documentation.
Sorry, something went wrong.
cwadhwani-splunk
No branches or pull requests
What is the sc4s version ?
3.22.5
Which operating system (including its version) are you using for hosting SC4S?
does not matter
Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S?
does not matter
Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support?
does not matter
Is the issue related to the environment of the customer or Software related issue?
no
Is it related to Data loss, please explain ?
Protocol? Hardware specs?
no
Last chance index/Fallback index?
no
Is the issue related to local customization?
no
Do we have all the default indexes created?
does not matter
Describe the bug
Current state:
The text was updated successfully, but these errors were encountered: