Simpler alternative about km HOT 3 CLOSED

Hi Vincent,

Thank you for taking the time to e-mail us your library. I agree with
you that your approach is much cleaner. Is it OK if we include your
library on our list of 3rd-party libraries here:
http://support.kissmetrics.com/apis/other?

-John

On Wed, Aug 24, 2011 at 10:57 PM, vbrendel
[email protected]
wrote:

Hi KM,

I had a few issues with your gem and eventually decided it was easier to create my own code to interface with Kissmetrics and would like to share it with you what the problems were and what I came up with.

The first problem was around environments and the use of logs and cron and I had to work around the fact that the code executes differently in production. I would recommend that rather than hardcode behavior around environments to make this configurable instead. For example, I use an environment called 'staging' which should behave exactly like production, except it has a different name.

Also, as you may know, Heroku only allows hourly cron jobs so that meant the stats were not instant. And then I didn't see a distinct advantage to holding the logs in a file since they are sent one-by-one anyway. Finally, using the file system, in particular the tmp dir for storing the log posed the potential problem of logs possibly being deleted by automatic cleanup processes.

Because Heroku works well with delayed_job, that was my preferred method for sending metrics.

So please find my version of the KM class in the gist below. It's a bit of a work in progress since it only does what I need but so far it works well for me.

https://gist.github.com/1170061 (required: delayed_job and httparty gems)

Thanks,
Vincent

Reply to this email directly or view it on GitHub:
#3

from km.

Hi John,

Absolutely, and I've now started a repo for it, so please feel free to
reference: https://github.com/vbrendel/delayed_km

Cheers,
Vincent

On Sat, Aug 27, 2011 at 1:56 AM, kmjbutler <
[email protected]>wrote:

Hi Vincent,

Thank you for taking the time to e-mail us your library. I agree with
you that your approach is much cleaner. Is it OK if we include your
library on our list of 3rd-party libraries here:
http://support.kissmetrics.com/apis/other?

-John

On Wed, Aug 24, 2011 at 10:57 PM, vbrendel
[email protected]
wrote:

Hi KM,

I had a few issues with your gem and eventually decided it was easier to
create my own code to interface with Kissmetrics and would like to share it
with you what the problems were and what I came up with.

The first problem was around environments and the use of logs and cron
and I had to work around the fact that the code executes differently in
production. I would recommend that rather than hardcode behavior around
environments to make this configurable instead. For example, I use an
environment called 'staging' which should behave exactly like production,
except it has a different name.

Also, as you may know, Heroku only allows hourly cron jobs so that meant
the stats were not instant. And then I didn't see a distinct advantage to
holding the logs in a file since they are sent one-by-one anyway. Finally,
using the file system, in particular the tmp dir for storing the log posed
the potential problem of logs possibly being deleted by automatic cleanup
processes.

Because Heroku works well with delayed_job, that was my preferred method
for sending metrics.

So please find my version of the KM class in the gist below. It's a bit
of a work in progress since it only does what I need but so far it works
well for me.

https://gist.github.com/1170061 (required: delayed_job and httparty
gems)

Thanks,
Vincent

Reply to this email directly or view it on GitHub:
#3

Reply to this email directly or view it on GitHub:
#3 (comment)

from km.

I've added it to our list: http://support.kissmetrics.com/apis/other.
Thanks again for your efforts!

-John

On Fri, Aug 26, 2011 at 6:08 PM, vbrendel
[email protected]
wrote:

Hi John,

Absolutely, and I've now started a repo for it, so please feel free to
reference: https://github.com/vbrendel/delayed_km

Cheers,
Vincent

On Sat, Aug 27, 2011 at 1:56 AM, kmjbutler <
[email protected]>wrote:

Hi Vincent,

Thank you for taking the time to e-mail us your library. I agree with
you that your approach is much cleaner. Is it OK if we include your
library on our list of 3rd-party libraries here:
http://support.kissmetrics.com/apis/other?

-John

On Wed, Aug 24, 2011 at 10:57 PM, vbrendel
[email protected]
wrote:

Hi KM,

I had a few issues with your gem and eventually decided it was easier to
create my own code to interface with Kissmetrics and would like to share it
with you what the problems were and what I came up with.

The first problem was around environments and the use of logs and cron
and I had to work around the fact that the code executes differently in
production. I would recommend that rather than hardcode behavior around
environments to make this configurable instead. For example, I use an
environment called 'staging' which should behave exactly like production,
except it has a different name.

Also, as you may know, Heroku only allows hourly cron jobs so that meant
the stats were not instant. And then I didn't see a distinct advantage to
holding the logs in a file since they are sent one-by-one anyway. Finally,
using the file system, in particular the tmp dir for storing the log posed
the potential problem of logs possibly being deleted by automatic cleanup
processes.

Because Heroku works well with delayed_job, that was my preferred method
for sending metrics.

So please find my version of the KM class in the gist below. It's a bit
of a work in progress since it only does what I need but so far it works
well for me.

https://gist.github.com/1170061 (required: delayed_job and httparty
gems)

Thanks,
Vincent

Reply to this email directly or view it on GitHub:
#3

Reply to this email directly or view it on GitHub:
#3 (comment)

Reply to this email directly or view it on GitHub:
#3 (comment)

from km.