Make it easier to work with open source Kadira

[merlinstardust]

Since Kadira APM is now open source and people will be spinning up their own instances, can the connect function include a URL to point to?

For example

Kadira.connect('<AppId>', '<AppSecret>', '<KadiraUrl>');

[danieltimpone]

@merlinpatt it seems like you can actually do that by passing options as a third arg to the connect function like this:

Kadira.connect('<AppId>', '<AppSecret>', { endpoint: '<KadiraUrl>' });

Unfortunately, I'm dealing w/ some auth issues using this approach. Lmk if you run into the same thing / figure it out.

[mneva]

Hi @merlinpatt and @danieltimpone did you get this to work?

[mjovkovic]

@merlinpatt you should be able to set ENV variable: KADIRA_OPTIONS_ENDPOINT to point to the Kadira engine. You have additional variables here.

I got it to connect to Kadira server using that, but I'm still not seeing any data.

EDIT: It turned out kadira RMA service was down, it works fine with KADIRA_OPTIONS_ENDPOINT property set!

[kodie]

I wrote an article about how I got Kadira up and running on a Digital Ocean droplet here: https://www.gethappyboards.com/2017/07/rolling-out-your-own-instance-of-kadira/