-
Notifications
You must be signed in to change notification settings - Fork 111
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
docs: update getting-started-splunk-setup.md #2417
Conversation
I can't quite figure out how the customer is supposed to use this. It reads as steps but they don't seem like actual guided tasks. Is it more of a best practices topic or an overview? Or if it is numbered steps/process, then maybe we add links to each step? I'd love to get your thoughts and maybe we can discuss in our 1:1
hi @jenworthington sure, that's what this section is about: Topic: how to setup your Splunk instance to work with SC4S Steps:
These are the two things that must be done to ensure SC4S-Splunk connection. Ad 1 Indexes Ad 2 HTTP event collector
|
partially solves #2358 |
@jenworthington can you work on the new file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check the comment.
@rjha-splunk I left the file that you saw for reference for Jen, but please check |
More edits, added some new links to the Splunk Enterprise docs
Thanks for the new suggestions for structure, it was really helpful. I think I've captured all of the requested changes, take a look and let me know, happy to work on this one some more as needed. |
@jenworthington ready for the next iteration |
@jenworthington something went wrong and your changes to |
I made these changes a while back but maybe i did something weird with the branching? So I redid them and hopefully second time is the charm. ;)
@jenworthington ready for the final pass |
final pass completed, I incorporated all of your suggestions, Maciek.
🎉 This PR is included in version 3.27.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
I can't quite figure out how the customer is supposed to use this. It reads as steps but they don't seem like actual guided tasks. Is it more of a best practices topic or an overview? Or if it is numbered steps/process, then maybe we add links to each step? I'd love to get your thoughts and maybe we can discuss in our 1:1