Notificatoin | Caution about catch all notifications

Open
#405 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Locate the documentation section covering notification rules and read the surrounding guidance. Update it to warn that catch-all notifications may hit per-notification rate limits and recommend spreading rules across several groups; correct the apparent spelling errors while preserving the intended meaning.

Written by the indexing model from the issue text.

Description

Rate limits apply per notification. Catch al notifications are likely to get rate-limited.

Good practice: Spread notification rules into several groups

Dominant language
CSS
Stars
1
Forks
2
Avg merge
2d 14h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flanksource/docs

All issues in flanksource/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.