We use cookies to ensure that we give you the best experience on our website. By continuing your visit on the website, you consent to the use of the cookies. If you want to find out more about the cookies we use, you can access our Privacy Policy.
This action is irreversible and cannot be undone. Please confirm your decision to continue.
Reject discussion
This action is irreversible and cannot be undone. Please confirm your decision to continue.
Feedback and Future Plans: Gregg's Presentation on Designing for Failure
Hi everyone,
We hope you all enjoyed Gregg's insightful presentation on designing for failure instead of chasing uptime. Gregg covered some significant points about transitioning from a traditional Push model to a Pull model for your data streams, using tools like AWS SQS to manage buffering and minimize data loss.
We'd love to hear your thoughts on the presentation.
- What were your key takeaways from Gregg's talk?
- Do you think the strategies he proposed are applicable to your current infrastructure?
- Are you considering implementing AWS SQS in your Splunk data streams? Why or why not?
- Have you tried similar approaches before, and what was your experience?
Let's get a discussion going and share our insights and plans for future-proofing our data systems.
Looking forward to your responses!
