We use it in production. It makes deploying serverless apps into multiple AWS accounts way easier. It also speeds up creating CloudFormation YAML templates a lot.
We watch addEventListener to do the callback timing which jQuery uses under the covers. Any requests going through the browser's xhr interface will get instrumented and reported (this is what $.get uses).
Based on what you said, it sounds like enabling this feature will have no impact on existing front-end load times. What about error reporting... are you guys satisfied with where it's at now or do you guys feel like there is more accurate and more in depth js error reporting in the future?
I had the same reaction. I believe using AGPL code within a website requires that the entire website be open sourced as AGPL. For nearly any company or non-AGPL project this is a huge barrier to using your project. Maybe someone with more legal knowledge can weigh in on if my understanding is accurate.
I think the biggest reason is the lack of good safe bike paths and infrastructure most places. As someone (in the US) who bikes nearly every day as my primary form of transportation I'm quick to admit that bike commuting is dangerous. I love it, but it requires constant vigilance and careful attention not to get hit by a car or a door (and I live in Portland which is much more bike friendly than most US cities). Bikers frequently share lanes with fast moving cars and it's very common for bike lanes to end unexpectedly, leaving the cyclist in a dangerous spot.
I'm willing to accept these risks, but for most people it's not worth it. My wife also enjoys biking, but hates to ride on busy streets for fear of ending up on the wrong end of a distracted motorist. This limits her options to weekend pleasure rides on dedicated bike paths.
The trick to getting more people to cycle is to invest heavily in bike path infrastructure so that more people will feel safe using it as a primary form of transportation.
- Spacey or dedicated lanes are a major requirement. And in my fantasies I'd like two kinds of lanes, speedy and casual. Riding around 25kmph for commuting can be dangerous if the lane thins out, people ride/run slow, kids play around.
- Also, secured parking spots. I refrain from riding when I don't know where I'm gonna park. Too easy to pick/steal https://www.youtube.com/watch?v=UGttmR2DTY8 . Or a <20 bucks tagging device (in 2013 it's probably easy for many manufacturers)
I am from Portland, as well. And the "bike friendly" claim seems like a joke after having lived in Amsterdam for nearly two years.
I don't think we (Portlanders) have a clue what bike-friendly is. It would be nice if biking in Portland were safe enough that you didn't have to wear a helmet - like it is here in Amsterdam. (I happen to be back over here in AMS for a month).
Portland, OR; Seattle, WA; SF - Rails developers, Mobile developers, C developers
New Relic is looking for developers to work on our world-class application monitoring products. We're looking for good people so feel free to apply even if you don't see the "perfect fit" on http://newrelic.com/about/jobs.
We’re a very fast growing pre-IPO start-up and we care about our culture.
We value:
* Work/Life Balance
* Respect
* Engineer Code Ownership
* Experimentation
Check out http://newrelic.com/about/jobs for more details.
INTERNs ok, no REMOTE, H1B maybe but these are hard to get now.
I work on New Relic's ruby agent, and you're right (hey Justin). In fact we support both methods (i.e. passing a timestamp or a duration). We rely on the front end server (e.g. nginx, apache) to set a timestamp in an HTTP header and forward that to the ruby application. In the case of heroku there is a special header that they pass which describes the queuing duration. Because we're in the ruby application we don't have control over whether this timestamp is accurate but I'm very interested in ideas on how we could do a better job in this situation.
We do provide javascript based browser instrumentation ("Real User Monitoring") which measures request time from the browser's perspective. This might give you a more accurate idea of what real users are experiencing in this case.
My thoughts before I left the project were to add increased granularity of queue times via having headers added at each passing server and show a rainbow chart for the 'depth' of queue at each layer, not sure if that ever got added.
There's facility for that in the Agent, to allow multiple copies of the header and use whichever came first (for the beginning) and whichever came last (for the end ), it'd be relatively easy to hook metrics into each of those.
New Relic, Portland, OR/San Francisco, CA/Seattle, WA
New Relic is looking for several developers to work on our world-class application monitoring product. If you have experience in Ruby, C, PHP, .NET, Java, Android, or Objective-C, you should check us out.
We’re a very fast growing pre-IPO start-up and we care about our culture.
New Relic, Portland, OR/San Francisco, CA/Seattle, WA
New Relic is looking for several developers to work on our world-class application monitoring product. If you have experience in Ruby, C, Java, Android, or Objective-C, you should check us out.
We’re a very fast growing pre-IPO start-up and we care about our culture.
New Relic is looking for a talented Ruby engineer to join a team developing what we call the Ruby Agent. The Ruby Agent is the instrumentation library that reports back to New Relic’s world-class application monitoring product. You probably know it as the newrelic_rpm gem.
We’re a very fast growing pre-IPO start-up and we care about our culture.
We value:
* Work/Life Balance
* Respect
* Engineer Code Ownership
* Experimentation
We also have several other positions we're looking to fill.
