============
Py-Analytics is a library designed to make it easy to provide analytics as part of any project.
The project's goal is to make it easy to store and retrieve analytics data. It does not provide
any means to visualize this data.
Currently, only ``Redis`` is supported for storing data.
Requirements
------------
Required
~~~~~~~~
Requirements **should** be handled by setuptools, but if they are not, you will need the following Python packages:
* nydus
* redis
* dateutil
Optional
~~~~~~~~
* hiredis
analytics.create_analytic_backend
----------------------------------
Creates an analytics object that allows to to store and retrieve metrics::
>>> from analytics import create_analytic_backend
>>>
>>> analytics = create_analytic_backend({
>>> 'backend': 'analytics.backends.redis.Redis',
>>> 'settings': {
>>> 'defaults': {
>>> 'host': 'localhost',
>>> 'port': 6379,
>>> 'db': 0,
>>> },
>>> 'hosts': [{'db': 0}, {'db': 1}, {'host': 'redis.example.org'}]
>>> },
>>> })
Internally, the ``Redis`` analytics backend uses ``nydus`` to distribute your metrics data over your cluster of redis instances.
There are two required arguements:
* ``backend``: full path to the backend class, which should extend analytics.backends.base.BaseAnalyticsBackend
* ``settings``: settings required to initialize the backend. For the ``Redis`` backend, this is a list of hosts
in your redis cluster.
Example Usage
-------------
::
from analytics import create_analytic_backend
import datetime
analytics = create_analytic_backend({
"backend": "analytics.backends.redis.Redis",
"settings": {
"hosts": [{"db": 5}]
},
})
#create some analytics data
analytics.track_metric("user:1234", "comment", datetime.date.today())
analytics.track_metric("user:1234", "comment", datetime.date.today(), inc_amt=3)
#retrieve analytics data:
analytics.get_metric_by_day("user:1234", "comment", datetime.date.today(), limit=20)
analytics.get_metric_by_week("user:1234", "comment", datetime.date.today(), limit=10)
analytics.get_metric_by_month("user:1234", "comment", datetime.date.today(), limit=6)
#create a counter
analytics.track_count("user:1245", "login")
analytics.track_count("user:1245", "login", inc_amt=3)
#retrieve a count
analytics.get_count("user:1245", "login")
TODO
----
* Add more backends (MySQL, Postgres, ...)
* Add an API so it can be deployed as a stand alone service
Metadata
Release files for analytics 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| analytics-0.2.1.tar.gz | 7.8 kB | Without provenance | Details for analytics-0.2.1.tar.gz |
Release files / analytics-0.2.1.tar.gz
| Download URL | analytics-0.2.1.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dbc11227395cbd5381d71d94ccd1b47d86a7bbe71c4e9d3017aa4d29b11edc9
|
|
BLAKE2b-256 checksum How to use checksums |
16e3360c36b7eb35013628c66c339b6dd42fdb7bfc2095230e3d8210ae280f78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for analytics 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.