micro-analytics/micro-analytics-cli

IP Blacklist

Open

#11 opened on 2017年1月11日

GitHub で見る
 (5 comments) (0 reactions) (0 assignees)JavaScript (738 stars) (52 forks)batch import
enhancementhelp wanted

説明

Obviously this could be implemented in the client-side on a per-project basis, but I think it would be a decent idea to implement some sort of IP blacklisting system so that stats don't get bloated during development/QA.

Maybe something along the lines of providing a .ipignore file that follows the same general rules of .gitignore files?

127.0.0.1
192.102.*
*.512.*

Again, not sure if you're trying to keep this as micro as possible leaving things like this up to the individual developer. But seems like a feature that many could benefit from.

コントリビューターガイド

技術スタック
javascriptnodejs
領域
backendanalytics
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
basic Node.js knowledgeunderstanding of .gitignore patterns
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
75
調査方針
Examine the request handling logic in the micro analytics cli codebase, likely in a file like index.js or lib/tracker.js, to see where IPs are captured. Look for any existing filtering or ignore mechanisms. The issue suggests implementing a .ipignore file with pattern matching similar to .gitignore. Consider adding a new module to parse and apply ignore rules. Check comments in the issue for any maintainer guidance on whether this feature is desired and any architectural preferences.