Maybe I didn't explain it well but in metrics-only mode, no data is
sent to our collector. Basically, the agent collects metrics
in-process and your agent.use() callback is the data sink. We have
more advanced options for clustered applications but that's the basic
mode of operation.
There was a "birds of a feather" session in Vancouver in August; my
co-worker Sam represented StrongLoop.
To the best of my knowledge, not much came of it and I suspect that's
because there is not much overlap in the wants and needs of the
stakeholders.
That meeting was about finding common ground in tracing-related needs to determine what can be done to improve the situation for everyone. It was somewhat successful at highlighting those commonalities too.
The issue is not a lack of consistency of tracing needs, but that the tooling to trace async js automatically doesn't exist and would thus require someone stepping up to develop it in the open and lead the community to start using it.
TJ Fontaine did a bit of experimentation with node-tracing, and Forrest Norvell made CLS. Trevor Norris had also created AsyncListener to track changes between async contexts. But all the approaches so far have been too naive or simplistic and ultimately flawed.
The largest obstacle I've seen to overcoming this is unwillingness or inability to put in the time or resources necessary and to work together to find a proper solution. Companies selling performance monitoring, including the one I work at, are focused on adding value to their own products. Putting significant effort into projects that devalue those is unappealing.
Until node APM products shift their core value to something beyond simply collecting and displaying data, those will remain features core to their product and thus often deemed not acceptable for significant open development.
The pursuit of competitive advantage can be problematic when it comes to underdeveloped markets such as this.
--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/467C8A86-27E5-4B5A-A3C4-2838E8EDDD0E%40g8o.net.
For more options, visit https://groups.google.com/d/optout.
On Tue, Nov 11, 2014 at 12:04 PM, Andreas Marschke
<andreas....@gmail.com> wrote:
> Hi Ben,
>
> thanks for your pointers.
>
> The fact that I need an API-key and have to (If I understand you correctly)
> still send my data to the service provider (in worst case
> even through the same network interface as my data I need to process comes
> in from) means I still have no control over my data
> and sorry but some more security conscious potential customers may take an
> issue with that. Besides the fact that I'll have to
> doubly saturate my existing bandwidth to get it somehwere else is slightly
> questionable. What I actually meant by "master of
> my own data" (granted the terminology is a bit messy here) is 1) I keep my
> data on my premises and get to validate and evaluate
> it myself. A solution (and still use StrongLoop) would be providing an
> appliance or installation package for "on-premise" deployment
> for StrongLoop.
Maybe I didn't explain it well but in metrics-only mode, no data is
sent to our collector. Basically, the agent collects metrics
in-process and your agent.use() callback is the data sink. We have
more advanced options for clustered applications but that's the basic
mode of operation.
> Since you said that the landscape is "scattered" regarding performance and
> profiling and the like. Would it be an improvement to
> commence something like a roundtable of the elders to start "Working Group"
> or (in theory more agile than a committee) that would
> define, support and create standards as to what to profile? Maybe even ask
> people from the Companies in the community (ie.
> yourself and breatheren) with blink/v8/node developers together and think of
> a proper way to guide community as a whole towards
> a common goal of a good standard and development of good tools. I've seen it
> work for years in the networking community (see
> RIPE working groups) sure there will be the occasional vitriol and
> unnecessary bikeshedding but if it helps more than a handful of
> developers to better understand the node environment from a performance
> point of view. This could be a sister project to what has
> been instantiated next to the recently unveiled nodejs group.
There was a "birds of a feather" session in Vancouver in August; my
co-worker Sam represented StrongLoop.
To the best of my knowledge, not much came of it and I suspect that's
because there is not much overlap in the wants and needs of the
stakeholders. About the only thing everyone could agree on is that it
would be great if we don't have to monkey-patch everything when
instrumenting applications and that is what Trevor Norris's
async-listener work is trying to do.
The situation is different from node-forward. With that project, it's
clear what the problems are that need to be addressed, and there is
broad consensus on how to make it happen.
TJ Fontaine did a bit of experimentation with node-tracing, and Forrest Norvell made CLS. Trevor Norris had also created AsyncListener to track changes between async contexts. But all the approaches so far have been too naive or simplistic and ultimately flawed.
--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/XYJih9Jv_40/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/7a021f0f-0f7f-444a-b6e3-e30c27a4871f%40googlegroups.com.
Unfortunately, Google/V8 doesn't really care about nodejs. They only care about the browser, for which they deem the WebKit inspector to be sufficient. StrongLoop put so much effort into their node-inspector port of those tools for that exact reason.
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CADq4APtj7MW6uJ%2BqipqT_1bBpddYU6ohgNJF1cw2V%3DrebtZbsQ%40mail.gmail.com.