Fill Hawkular-APM with Lightbright traces

[lance]

• Finish the data mapping between lightbright and hawkular-apm json.
• Avoid trace data polution on hawkular-apm-server from roi module.

[helio-frota]

More information:
#11

[lance]

Ref: https://github.com/bucharest-gold/lightbright/milestone/1

[helio-frota]

Now is more easy to identify any difference from roi trace data
bucharest-gold/hawkular-apm-client#5 (comment)

Instead send to hawkular-server:
https://github.com/bucharest-gold/hawkular-apm-client/blob/master/index.js#L70

We send to console.log();

Because the FakeApp is calling publishTraces here:
https://github.com/bucharest-gold/hawkular-apm-client/blob/master/test/app-fixture.js#L24

Then we can see if has any difference with roi usage.

[helio-frota]

https://gist.github.com/helio-frota/2e287c3b22a275e9a8e5762571cf6e37

[helio-frota]

#7 (comment)
We don't need to worry about this anymore, all the tests are showing the same thing please see the gist ^^

[helio-frota]

From lance:
#11 (comment)

We are using these attributes:
https://github.com/bucharest-gold/hawkular-apm-client/blob/master/index.js#L51-L62

[helio-frota]

When accessing the example App multiple times, then new wrapers/handlers arise.

I have no idea if this is correct/expected:
https://gist.github.com/helio-frota/bf11e2409fa908c7eda2cb0dd37522f3

Every time the text appears on the gist is one access to example app url:
"Traces added to hawkular-apm-server."

[helio-frota]

[lance]

After discussing this with @balunasj we've decided to close this issue, and track progress towards this in bucharest-gold/lightbright since the implementation of any given data format would probably be most efficiently accomplished as a lightbright filter. See: bucharest-gold/lightbright#11.