[
https://issues.apache.org/jira/browse/IGNITE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546989#comment-14546989
]
Nikita Ivanov commented on IGNITE-911:
--------------------------------------
Attached is the basic implementation for Mixpanel integration. Few comments:
- Go to https://mixpanel.com/register and register for a free account. This
account will have to be publicly available to the community. GridGain or other
vendor can provide a paid account once the number of events will grow.
- You'll need two additional libs: JSON
http://mvnrepository.com/artifact/org.json/json/20141113, and Java Mixpanel
API: https://mixpanel.com/help/reference/java
- Attached is the Scala source code for a simple "generic" manager that
provides simple API for sending events to Mixpanel service.
- One limitation of this implementation is that in case of Mixpanel outage it
doesn't buffer events for resending - it simply drops the events in such
situation.
- Example: In Ignite code simply use {{MixpanelManager.event("ignite-start")}}
to log a ignite start event.
- To see events in Mixpanel - log in and go to "Live View" on the left side.
Events are sent in bulk with a configurable timeout.
> Provide MixPanel integration.
> -----------------------------
>
> Key: IGNITE-911
> URL: https://issues.apache.org/jira/browse/IGNITE-911
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: sprint-4
> Reporter: Nikita Ivanov
> Assignee: Nikita Ivanov
> Fix For: sprint-5
>
> Attachments: mixpanel.scala
>
>
> Basically, we need to switch to a normal Mixpanel in-app analytics to
> tracking feature usage, exceptions and usage statistics to make Ignite a
> better product through better understanding how it's used for the users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
