Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How can my application send logs to different index's for compliance purposes
See original GitHub issueWhat happened: Currently i can send all the logs from a pod to a single index. What you expected to happen: We are migrating a lot of EC2 based application to EKS. Some security related logs on ec2 were written on file system and then sent to different index due to retention policy being higher compared to regular log file. In containers all logs go to a single index. Is there a way my application running on a k8s pod can send this to a different index ? How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment: EKS
- Kubernetes version (use
kubectl version): 1.14 - Ruby version (use
ruby --version): - OS (e.g:
cat /etc/os-release): Amaxon Linux 2 - Splunk version:
- Others:
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@limlengchye could you share the custom conf you are providing to send use multiple HEC token? i think it could be helpful if we can make it more native as well.
@matthewmodestino just a gentle reminder