We would be interested to explore feeding SnowPlow (https://github.com/snowplow/snowplow) atomic web analytics data into Bitdeli: potentially our SnowPlow StorageLoader (which currently feeds Infobright) could fire all SnowPlow events into Bitdeli using your Events API.
A couple of questions about your Events API:
1: does your Events API only support submitting one event at a time? Would be nice to bulk them up otherwise we're going to be creating 1000s of HTTP connections.
2: is there a reason why you pull uid up out of the event's JSON envelope, but not the event type? It's nice to have the event type outside of the envelope, because then you can know the expected structure of the JSON without having to look inside it. Just a thought - this is how MixPanel and Fluentd do it, and it's something we're moving to supporting for SnowPlow.
Anyway, have a think about feeding Bitdeli with SnowPlow event data and let me know if it's something you want to collaborate on! And keep up the great work in the meantime.
Feeding data from SnowPlow to Bitdeli sounds like a great idea.
1. It does, although it is an undocumented feature. You can send a list of events instead of a single JSON object to the Events API.
2. Bitdeli doesn't need an event type but it needs a user identifier. The event type is utilized with the data sources that provide it, like Mixpanel, but for instance our integration to the GitHub commits API doesn't expect that events contain a type.
A good starting point would be to create a super simple card that does something with the data from SnowPlow, like
Great stuff Vtuulos - I have signed up. Will probably take us a few weeks to get round to it as we have a few other releases which need to happen first...
Comments
Hey vtuulos, this looks really cool.
We would be interested to explore feeding SnowPlow (https://github.com/snowplow/snowplow) atomic web analytics data into Bitdeli: potentially our SnowPlow StorageLoader (which currently feeds Infobright) could fire all SnowPlow events into Bitdeli using your Events API.
A couple of questions about your Events API:
1: does your Events API only support submitting one event at a time? Would be nice to bulk them up otherwise we're going to be creating 1000s of HTTP connections.
2: is there a reason why you pull uid up out of the event's JSON envelope, but not the event type? It's nice to have the event type outside of the envelope, because then you can know the expected structure of the JSON without having to look inside it. Just a thought - this is how MixPanel and Fluentd do it, and it's something we're moving to supporting for SnowPlow.
Anyway, have a think about feeding Bitdeli with SnowPlow event data and let me know if it's something you want to collaborate on! And keep up the great work in the meantime.
Feeding data from SnowPlow to Bitdeli sounds like a great idea.
1. It does, although it is an undocumented feature. You can send a list of events instead of a single JSON object to the Events API.
2. Bitdeli doesn't need an event type but it needs a user identifier. The event type is utilized with the data sources that provide it, like Mixpanel, but for instance our integration to the GitHub commits API doesn't expect that events contain a type.
A good starting point would be to create a super simple card that does something with the data from SnowPlow, like
https://github.com/bitdeli/bd-rawevents-event-volume/blob/ma...
that just counts the number of events received over time.
Let me know if you want to give it a try - I am happy to extend your trial as long as needed.
Great stuff Vtuulos - I have signed up. Will probably take us a few weeks to get round to it as we have a few other releases which need to happen first...