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

Request - exclusionList in Alert should filter on more than just the message #418

Open
philipsabri opened this issue Sep 12, 2022 · 1 comment · May be fixed by #419
Open

Request - exclusionList in Alert should filter on more than just the message #418

philipsabri opened this issue Sep 12, 2022 · 1 comment · May be fixed by #419

Comments

@philipsabri
Copy link

philipsabri commented Sep 12, 2022

Hello! Currently running into a few problems with more "complex" Alert configs.

Would be nice if we could use exclusionList on more than just the message such as the name of the alert, which I believe is called event.InvolvedObject.Name

I would like to run something like this without having to hardcore all services in eventSources for the first Alert config but still be able to add more customizable slack messages on only some services.

apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: service-deploy
  namespace: flux-system
spec:
  summary: "HelmRelease deploys"
  providerRef:
    name: slack-service-deploy
  eventSeverity: info
  eventSources:
    - kind: HelmRelease
      name: "*"
  exclusionList:
    - ".*flurrens-service.*"
---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: service-deploy-flurren
  namespace: flux-system
spec:
  summary: "tex text notify owner <@SLACK_ID_HERE>"
  providerRef:
    name: slack-service-deploy
  eventSeverity: info
  eventSources:
    - kind: HelmRelease
      name: "*"
      matchLabels:
        owner: flurren
@philipsabri
Copy link
Author

Made a PR if this could be something #419 I dont know GO so it could probably be done in other ways.

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

Successfully merging a pull request may close this issue.

1 participant