No project description provided
Project description
Overview
MI project collects data from GitHub repositories. You can use it to either collect data stored locally or within Amazon’s S3 cloud. For personal usage, checkout <Usage> section.
Together with mi-scheduler, we provide automated data extraction pipeline for data minig of requested repositories and organizations. This pipeline can be scheduled customly, e.g. to run daily, weekly, and so on.
Data extraction request
To request data extraction for repository or organization, create Data Extraction Issue in MI-Scheduler repository. Use this link TODO
Data extraction Pipeline (diagram)
MI pipeline is simple to understand, see diagram below
+---------+
|ConfigMap|
+----+----+
|
+--+-------+--------+--+
| | | |
| | mi-scheduler | |
| | | |
+------+---+---+-------+
| | | | |
| | | | |
| | | | |
| Argo Workflows |
| | | | |
| | | | |
+---------------v---v---v---v----v------------------+ +-------------------- +--------------------+
| | | Visualization | | Recommendation |
| +---------+ +---------+ +---------+ | +-------------------+ +--------------------+
| |thoth/ | | AICoE | | your | | | Project Health | | thoth |
| | station| | | | org | | | (dashboard) | | |
| +---------+ +---------+ +---------+ | | | | |
| |solver | |... | |your | | +---------+---------+ +----------+---------+
| | | | | | repos | | thoth-station/mi ^ ^
| |amun | |... | X X X X X | | | (Meta-information Indicators) | |
| | | | | | | | +-------------+---------------+
| |adviser | |... | | | | |
| | | | | | | | |
| |.... | |... | | | | +-----------------+-------------------+
| | | | | | | | | |
| +---------+ +---------+ +---------+ | | Knowledge Processsing |
| | | |
+-----------------------+---------------------------+ +-----------------+-------------------+
GitHub repositories | ^
| +--------------------------------------------------------+ |
| | | |
| | Entities Analysis +-------> Knowledge | |
+---------------->-+ +--------------------+
+---------+----------------+----------+------------------+
| Issues | Pull Requests | Readmes | etc........... |
| | | | |
+---------+----------------+----------+------------------+
What can MI extract from GitHub?
MI analyses entities specified on the srcopsmetrics/entities page Entity is essentialy a repository metadata that is being inspected (e.g. Issue or Pull Request), from which specified features are extracted and are stored to dataframe.
MI is essentialy wrapped around PyGitHub module to provide careless data extraction with API rate limit handling and data updating.
Install
pip
MI is available through PyPI, so you can do
pip install srcopsmetrics
git
Alternatively, you can install srcopsmetrics by cloning repository
git clone https://github.com/thoth-station/mi.git
cd mi
pipenv install --dev
Usage
Setup
To store data locally, use -l when calling CLI or set is_local=True when using MI as a module.
By default MI will try to store the data on Ceph. In order to store on Ceph you need to provide the following env variables:
S3_ENDPOINT_URL Ceph Host name
CEPH_BUCKET Ceph Bucket name
CEPH_BUCKET_PREFIX Ceph Prefix
CEPH_KEY_ID Ceph Key ID
CEPH_SECRET_KEY Ceph Secret Key
For more information about Ceph storing look here
CLI
See –help for all available options
See some of the examples below
Get repository PullRequest data locally
srcopsmetrics --create --is-local --repository foo_repo --entities PullRequest
which is equivalent to
srcopsmetrics -clr foo_repo -e PullRequest
Get organization PR data locally
srcopsmetrics -clo foo_org -e PullRequest
Get multiple repository PR data locally
srcopsmetrics -clr foo_repo,bar_repo -e PullRequest
Get multiple entity data locally
srcopsmetrics -clr foo_repo -e PullRequest,Issue,Commit
Meta-Information Entities Metrics
To know more about indicators that are extracted from data, check out Meta-Information Indicators.
How to contribute
Always feel free to open new Issues or engage in already existing ones!
Custom Entities & Metrics
If you want to contribute by adding new entity or metric that will be analysed from GitHub repositories, feel free to open up an Issue and describe why do you think this new entity should be analysed and what are the benefits of doing so according to the goal of thoth-station/mi project.
After creating Issue, you can wait for the response of thoth-station devs Do not forget to reference the Issue in your Pull Request.
Implementation
Look at Template entity to get an idea for requirements that need to be satisfied for custom entity implementation.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file srcopsmetrics-2.6.3.tar.gz
.
File metadata
- Download URL: srcopsmetrics-2.6.3.tar.gz
- Upload date:
- Size: 34.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/39.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.8
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 846ecfaff0f770f4afd229668b21a530138162c8576ca0d0e3acc094a2365daa |
|
MD5 | 81869c8d33e715bae6fbdf34313c1334 |
|
BLAKE2b-256 | 56d1c124cf660fa8202e73f23a271bf894cca9e70fa9424574663d07c52f20e0 |
File details
Details for the file srcopsmetrics-2.6.3-py3-none-any.whl
.
File metadata
- Download URL: srcopsmetrics-2.6.3-py3-none-any.whl
- Upload date:
- Size: 60.1 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/39.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.8
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 2a595caa70b4d2875b6e858ed4ea214f032ba89e0026fac1ec8d9a2adb6617eb |
|
MD5 | 1763a69df0819cda86069adb0d45855e |
|
BLAKE2b-256 | 0a50a92bca818c1581f97e628ef5f0e63ed2be4b869507268df54b61e7b03f80 |