Skip to content
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

Filter out some workflows/jobs #68

Open
fbarbare opened this issue Sep 3, 2024 · 0 comments
Open

Filter out some workflows/jobs #68

fbarbare opened this issue Sep 3, 2024 · 0 comments

Comments

@fbarbare
Copy link

fbarbare commented Sep 3, 2024

This integartion sends quite a lot of spans to Sentry and we would like to reduce it to not go over the quota that we're paying for. In order to do that, we would like to disable this integration for some of the workflows/jobs that we have since they are not critical and quite basic. Some only run for a few seconds.

I think we could include some configuration in the sentry_config.ini so that we can include/exclude some workflows.

I was thinking that we could have a structure that would look like this in JSON:

{
  "dsn": "https://[email protected]/foobar",
  "include_workflows": [
    {"repo": "repo-1", "workflow": "workflow1.yml"},
    {"repo": "repo-2", "workflow": "workflow1.yml"}
  ],
  "exclude_workflows": [
    {"repo": "repo-1", "workflow": "workflow2.yml"},
    {"repo": "repo-2", "workflow": "workflow2.yml"}
  ]
}

which seem to look like this in .ini file (might be wrong, I don't know much about those):

dsn=https://[email protected]/foobar
include_workflows[]={"repo":"repo-1","workflow":"workflow1.yml"}
include_workflows[]={"repo":"repo-2","workflow":"workflow1.yml"}
exclude_workflows[]={"repo":"repo-1","workflow":"workflow2.yml"}
exclude_workflows[]={"repo":"repo-2","workflow":"workflow2.yml"}

I could work on something like that and submit a PR. What are your thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant