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

Add channel/channel_id in slack properties #365

Closed
igoritos22 opened this issue Sep 5, 2022 · 4 comments
Closed

Add channel/channel_id in slack properties #365

igoritos22 opened this issue Sep 5, 2022 · 4 comments
Labels
kind/feature New feature or request lifecycle/rotten
Milestone

Comments

@igoritos22
Copy link

There may be some situations where it is necessary to pass a specific channel in the slack message post. It would be interesting to have something like this:

  slack:
    # -- Slack Webhook URL (ex: <https://hooks.slack.com/services/XXXX/YYYY/ZZZZ>), if not `empty`, Slack output is *enabled*
    webhookurl: ""
    # -- Slack Footer
    channel: ""
    # -- Channel ID
    footer: ""
    # -- Slack icon (avatar)
    icon: ""
    # -- Slack username
    username: ""
    # -- `all` (default), `text` (only text is displayed in Slack), `fields` (only fields are displayed in Slack)
    outputformat: "all"
    # -- minimum priority of event to use this output, order is `emergency\|alert\|critical\|error\|warning\|notice\|informational\|debug or ""`
    minimumpriority: ""
    # -- a Go template to format Slack Text above Attachment, displayed in addition to the output from `slack.outputformat`. If empty, no Text is displayed before Attachment
    messageformat: ""
@igoritos22 igoritos22 added the kind/feature New feature or request label Sep 5, 2022
@Issif
Copy link
Member

Issif commented Sep 7, 2022

I'll add the feature asap.

@Issif Issif moved this to To do in Falcosidekick 2.x Sep 7, 2022
@Issif Issif added this to the 2.27.0 milestone Sep 7, 2022
@Issif
Copy link
Member

Issif commented Sep 8, 2022

the PR is merged, it will be in next release

@Issif Issif moved this from To do to In progress in Falcosidekick 2.x Nov 29, 2022
@poiana
Copy link

poiana commented Dec 7, 2022

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@Issif Issif moved this from In progress to Done in Falcosidekick 2.x Jan 6, 2023
@poiana
Copy link

poiana commented Jan 6, 2023

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/rotten
Projects
Status: Done
Development

No branches or pull requests

3 participants