Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 1 May 2015 18:20:06 +0000 (UTC)
From: "Nikita Ivanov (JIRA)" <jira@apache.org>
To: dev@ignite.incubator.apache.org
Message-ID: <JIRA.12826608.1430504396000.48483.1430504406380@Atlassian.JIRA>
In-Reply-To: <JIRA.12826608.1430504396000@Atlassian.JIRA>
References: <JIRA.12826608.1430504396000@Atlassian.JIRA>
 <JIRA.12826608.1430504396688@arcas>
Subject: [jira] [Created] (IGNITE-852) Add in-app analytics to better
 understand usage and failure patterns.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Nikita Ivanov created IGNITE-852:
------------------------------------

             Summary: Add in-app analytics to better understand usage and failure patterns.
                 Key: IGNITE-852
                 URL: https://issues.apache.org/jira/browse/IGNITE-852
             Project: Ignite
          Issue Type: Bug
          Components: general
    Affects Versions: sprint-2
            Reporter: Nikita Ivanov
            Assignee: Nikita Ivanov
             Fix For: sprint-5


Basically, we need to follow the path of the most modern apps where they use combination of segment.io + mixpanels (or similar stack) for in-application analytics. This allows to track:
- how each individual feature or sub-system is used
- what OS/JVM version combinations are used by users
- exception/assertions (including details)
- performance metrics
- etc.

All this, of course, can be done w/o tracking or storing any sensitive user information, i.e. in anonymous mode.

Having this type of data will allow the community to make *much more* educated decisions on what to work on, what to fix first and what to test and in what priority.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)