newrelic

I have a project that uses the gradle build system and I'm willing to add New Relic monitoring to it. The project (including New Relic) is working fine on Linux (Fedora 20), but won't build on my Mac development system, and gives out an error stating Agent JAR loaded but agent failed to initialize . Here is the full log of the error: Dev-1:test 0x4d$ ./gradlew clean > Configuring > 1/2 projects > :appobjc[4437]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents

In our Rails app we rescue most of the exceptions on ApplicationController to give correct API response, but still want to track errors happening using ErrorCollector. Is there a way to manually send error to NewRelic? nort Based on what I see in the New Relic agent code you can do NewRelic::Agent.notice_error(exception, options) I have tested this and have this running in my stack Here's an example in a controller: class ApplicationController < ActionController::Base rescue_from ActiveRecord::RecordInvalid, with: :rescue_invalid_record private def rescue_invalid_record(exception) NewRelic:

I'm monitoring a PHP app with NewRelic, and I'm very confused about some of the numbers shown in the overview of my application. My app consists of a PHP webapp, that serves pages to web browsers on one side (obviously :), and performs requests to a Java backend on the other side: Browser <--> PHP Webapp --> Java Backend I know for a fact that some of the Java backend requests can take up to 15 seconds to complete, leading to the complete webapp from the point of view of the browser taking that much time. In the overview panel of newrelic (APM > My App > Monitoring > Overview), it says that my

I was diving into a really long request to one of my Rails applications using NewRelic and found a number of SQL queries that appear entirely foreign that are taking up a significant length of time. I've Google'd around but I've come up empty handed as to what they are, let alone whether I can prevent them from occurring. SELECT COUNT(*) FROM pg_class c LEFT JOIN pg_namespace n ON n.oid = c.relnamespace WHERE c.relkind in (?, ?) AND c.relname = ? AND n.nspname = ANY (current_schemas(false)) …and… SELECT a.attname, format_type(a.atttypid, a.atttypmod), pg_get_expr(d.adbin, d.adrelid), a

Where should I call NewRelic.Api.Agent.NewRelic.IgnoreApdex() or NewRelic.Api.Agent.NewRelic.IgnoreTransaction() in my SignalR hubs to prevent long-running persistent connections from overshadowing my application monitoring logs? Oooh, great question and one I hadn't thought about yet myself. I think what you would have to do is write a custom module, since modules execute before all handlers, that detect that the SignalR AspNetHandler handler is the one being requested and, if so, call the NewRelic IgnoreXXX methods at that point. Just spitballing (e.g. I haven't tested this) that module

Anytime I try to build my project I keep getting this error: Execution failed for task ':app:processReleaseGoogleServices'. No matching client found for package name 'com.my.package' I have made and remade the google-services.json and have used the app and the package com.my.package . Here's my project build.gradle: buildscript { repositories { ... } dependencies { classpath 'com.android.tools.build:gradle:2.0.0-beta6' classpath 'com.github.JakeWharton:sdk-manager-plugin:220bf7a88a7072df3ed16dc8466fb144f2817070' classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8' classpath 'io.fabric

I've created an Android app using Android Studio beta 0.8.2 and all was going well until the last few days when i started getting this exception just as i run it: 07-24 14:50:11.044 1176-1176/com.vme.vme I/Crashlytics﹕ Initializing Crashlytics 1.1.11.10 07-24 14:50:11.764 2325-2325/system_process D/MobileDataStateTracker﹕ default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default 07-24 14:50:11.769 2325-2325/system_process D/MobileDataStateTracker﹕ default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified) 07-24 14:50:15.079 1176-1176/com.vme.vme W

We picked up quite a high number of ajax calls taking a significant amount of time in AcquireRequestState, in our travels we stumbled upon the session locking gem in ASP.Net so we implemented a custom session state handler (Based on link below). After making the change and deploying it, we saw a very sharp drop in AcquireRequestState but it had been replaced with PreExecuteRequestHandler. This morning it suddenly dawned on me that we had included OWIN which was probably the reason for the PreExecuteRequestHandler taking up so much time. I then proceeded to remove that and the moment I deployed