micro-analytics/micro-analytics-cli

IP Blacklist

Open

#11 opened on Jan 11, 2017

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (738 stars) (52 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
backendanalytics
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Node.js knowledgeunderstanding of .gitignore patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
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.