You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now mage cannot send messages if the production switch is not set to 1. But when that is done, it expects a working configuration of Librato(Collectd). This dependency makes it hard to test in a live environment, especially because Librato is not a free service.
I am suggesting we provide a switch that can allow mage to send messages to rapidpro even with the production switch off. Or make Librato an optional dependency in production.
The text was updated successfully, but these errors were encountered:
We could update this so that if you don't provide a Librato key, then calls to the analytics functions are just NOOPs, regardless of the value of production
On Wed, Oct 14, 2015 at 2:35 AM, Rowan Seymour [email protected]
wrote:
We could update this so that if you don't provide a Librato key, then
calls to the analytics functions are just NOOPs, regardless of the value of
production
—
Reply to this email directly or view it on GitHub #2 (comment).
Right now mage cannot send messages if the production switch is not set to 1. But when that is done, it expects a working configuration of Librato(Collectd). This dependency makes it hard to test in a live environment, especially because Librato is not a free service.
I am suggesting we provide a switch that can allow mage to send messages to rapidpro even with the
production
switch off. Or make Librato an optional dependency in production.The text was updated successfully, but these errors were encountered: