With Cribl Stream’s GitOps features, you can manage Cribl Stream configuration with standard version-control systems and CI/CD flow. You can separate development from production configurations, and thus, safely build and continuously deploy your observability pipelines. The production environment will be read-only, and thus strongly protected against unauthorized or unintended changes. This intentionally restrictive approach is a good fit for some but not all organizations.
Here are some best practices and tips to consider when thinking about using a git strategy:
- Create a private repository. There will be some proprietary information that you won’t want to be public.
- Grant access to users as per-need basis. You want to keep full control over who can approve pipelines and packs to move from dev to prod.
- Examine the git.ignore file carefully. Know which default values are considered worthy of ignoring versus adding when Cribl pushes configurations from a local to remote Git repository.
- Use Git as a backup to restore an environment. Store critical configurations so you can revert back to a previous environment if you run into any issues.
- Use declarative comments. Details will help with understanding configuration changes and troubleshooting problems effectively.
- Choose branches over repositories. This provides a more efficient and cohesive development environment and enables a pull request feature.
- Worker/Global Commit and Deploy. When you make changes and commit on a global scope, you should push changes across multiple Cribl workers.
- Continuous Push and Commit. This contributes to a more agile and efficient development process by giving rapid feedback and improving collaboration.
Want to know more? Check out this post for a detailed customer use case and deep dive video!