Skip to content

Conversation

@rajatagarwal-ibm
Copy link
Member

Description

  • Define which sysdig metrics must be collected.

  • Add the metrics_filter field to the sysdig-agent configmap in helm
    chart to control which sysdig metrics should be collected.

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

  • When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
  • Merge by using "Squash and merge".

@rajatagarwal-ibm
Copy link
Member Author

/run pipeline

@ocofaigh ocofaigh merged commit 1e46628 into main Oct 4, 2023
@ocofaigh ocofaigh deleted the sysdig-metrics branch October 4, 2023 14:59
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants