alpgarcia
commented
5 years ago The available aliases are listed below. Documentation is partially available, so I'll try to add a brief description of each index to give you a quick glance of what they contain. Please ask us whatever you may need. Those aliases with more complete documentation are linked to those docs.
Some general notes:
- As a rule of the thumb, use always field whose names are written in lower case.
- Fields coming from SortingHat, our tool to manage identities and their affiliations,
are
author_name,author_org_name,author_uuid,author_botandauthor_user_name. In some indexes we have similar fields for other participants like assignees. They are easily recognizable as the suffixes are always the same. - Discover tab is a good place to explore information.
- Table is based in aliases. From (Kibana Dev Tools)[https://sotrar.mozilla.community/app/kibana#/dev_tools] or from command line (e.g. using curl) you can get the list of aliases and the indexes they are pointing to with API requests like:
GET _cat/aliases?v
GET _cat/aliases/affiliations?v
| alias | description |
|---|---|
| [git](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/git.csv) | Each document corresponds to a commit. |
| [affiliations](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/affiliations.csv) | Groups indexes corresponding to single data sources to allow building visualizations in Kibana that contain info from all of them, see [https://sotrar.mozilla.community/app/kibana#/dashboard/Affiliations](Affiliations panel) under Community entry in the top menu. |
| [all_onion](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/onion.csv) | Groups all indexes containing pre-computed data based on onion analysis, see [Community -> Overall panel](https://sotrar.mozilla.community/app/kibana#/dashboard/Overall-Community-Structure). See also [panel documentation](https://chaoss.github.io/grimoirelab-sigils/panels/overall-community-structure/) to know more about it. |
| bugzilla | Each document correspond to an issue in Bugzilla, with info about the creator and the assignee. |
| demographics | Groups indexes that contain information for building [demographics panel](https://sotrar.mozilla.community/app/kibana#/dashboard/15e4b020-d075-11e8-8aac-ef7fd4d8cbad). See [https://chaoss.github.io/grimoirelab-sigils/panels/demographics/](panel documentation) to get some details, but basically for Mozilla it points only to Git index, which includes a couple of fields `demography_min_date` and `demography_max_date` not listed in its CSV ([pull request sent](https://github.com/chaoss/grimoirelab-elk/pull/580)) storing the dates of the first and the last contribution made for the corresponding author.
| discourse | Contains questions, answers and accepted answers as separate elements. Explore [Discover tab](https://sotrar.mozilla.community/goto/a6640ddcbe0573e46c06a6c8ebc141a8) to understand a bit better how it is built. |
| [git-emergintech](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/git.csv) | Same as `git` but filtered for emerging tech repositories only. |
| [git_areas_of_code](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/areas_of_code.csv) | Built from the same RAW information as Git, but focused at the level of file, see [Areas of Code panel](https://sotrar.mozilla.community/app/kibana#/dashboard/Git-Areas-of-Code) to have an idea of the info we have there. Each document is a file instead of being a commit as it is in Git index. |
| [github_issues](https://github.com/chaoss/grimoirelab-elk/blob/master/schema/github_issues.csv) | Documents can be either `issues` or `pull requests`. Use boolean field `pull_request` for filtering. |
| github-emergingtech | Same as `github_issues` but filtered for emerging tech repositories only. |
| meetup | Documents can be meetups, comments or rsvps. There are three fields named `ìs_meetup_<event_type>` of type long, which value will be 1 for the corresponding `<event_type> = ( meetup OR comment OR rsvp )`. There is also a `type` String field containing this information. See Meetup panels in the Dashboard to get some examples on how we use these fields. For instance see [meetups table](https://sotrar.mozilla.community/goto/f719b7e88b1c75c6f5a0a07544da54d1), built on top of a search for filtering in only meetups.|
| meetup-emergingtech | Same as `meetup` but filtered for emerging tech meetups only. |
| remo-activities | Contains information about Mozilla activities. See [Activities panel](https://sotrar.mozilla.community/app/kibana#/dashboard/Reps-Activities) to get an idea of what kind of information it contains. In short, it contains information about participants and mentors from the point of view of the activities. |
| remo-events | Contains information about Mozilla events. Each document corresponds to an event. See [Mozilla Reps, Events panel](https://sotrar.mozilla.community/app/kibana#/dashboard/Reps-Events) to have a look at the information we store in the index. |
| stackoverflow | Documents are questions and answers. Some info is shared in both, questions and their corresponding answers in order to be able to correctly filter in the dashboard. Questions also contains fields like `answer_count` to store the number of answers in order to easily show it in the panels. Accepted answers are marked using `ìs_accepted` boolean field and `is_accepted_answer` long field (used for counts). |
| stackoverflow-emergingtech | Same as `stackoverflow` but filtered for emerging tech. |
I'll keep this open to let you use this issue to ask us whatever else you may need.
havardl
edin-ogtal
canasdiaz
Our A&T folks need a list of the endpoints (credentials are already send) and the indexes they have to query. In order to make their life easier Bitergia will provide a small explanation of each index and links to documentation if available.