parse-community / parse-community/parse-server

Add usage analytics to Parse Server

Open
#7,993 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

New Feature / Enhancement Checklist
Current Limitation

There is no data source to estimate the common usage of Parse Server and its common configurations. That poses a challenge for strategic decision making in engineering and product management.

Feature / Enhancement Description

Anonymously collect analytics data about Parse Server usage. Similar to how Flutter SDK collects usage data:

The Flutter tool anonymously reports feature usage statistics and basic crash reports to help improve
Flutter tools over time. See Google's privacy policy: https://www.google.com/intl/en/policies/privacy/

https://github.com/flutter/flutter/blob/989f864497f59308896e8694c7d5d6a4ee65b36a/packages/flutter_tools/lib/src/reporting/first_run.dart#L15-L39

Characteristics:

  • Analytics data is collected anonymously
  • Parse Server provides a config option to disable the collection of analytics data (enabled by default)
  • Log a message on server start-up if data collection is enabled
  • Clearly describe the default data collection in the docs
  • Don't run analytics already on package install; the disclaimer has to logged prior to data collection
  • Publish privacy policy for Parse Platform org
Example Use Case

n/a

Alternatives / Workarounds

n/a

3rd Party References

Flutter SDK

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.

Research direction

Start by reviewing the referenced Flutter analytics implementation and then trace Parse Server's startup and configuration entry points. Define the anonymous data, opt-out behavior, startup notice, documentation, and privacy-policy requirements before implementation; done means these requirements are specified and covered across the server and docs.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
analytics, backend, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.