Loading Profile...
Recent activity
Subscribe to this feed-
Mike Ball started following the problem "Mongrel instances disappearing from configured application" in New Relic.
-
Mike Ball started following the problem "My iPhone battery drains too much overnight!" in Apple.
-
Mike Ball replied on February 20, 2009 20:23 to the question "Can I keep certain requests from being logged?" in New Relic:
That exactly what I was looking for. I knew I had seed a detailed example of it, and I finally found it.
http://sites.google.com/a/newrelic.co... -
Mike Ball asked a question in New Relic on February 19, 2009 23:02:
Can I keep certain requests from being logged?We have an action in our app that is only used when our load balancer checks to see if that mongrel is running; /healthcheck.
Because our load balancer calls this request constantly most of our requests in newrelic are for this action. Is there a way we can tell newrelic to completely ignore this action? I'm thinking of not even sending data for these requests to newrelic, but if the newrelic report can "filter out" certain actions, that would work as well. -
Mike Ball replied on February 17, 2009 20:26 to the question "How do I use filter_parameters with params capturing?" in New Relic:
I don't think I need an example. Looks like there are examples on the rails API.
http://api.rubyonrails.com/classes/Ac...
I'd recommend you change your comments in the newrelic.yml file to say "filter_parameter_logging" instead of "filter_parameters".
Thanks! -
Mike Ball asked a question in New Relic on February 13, 2009 17:25:
Is it normal for mongrel to never release memory?We just started using NewRelic for performance monitoring (it's
awesome btw). It has given us a lot of insight into how our
application is running.
One thing we've noticed is memory usage. Our mongrels normally take up
about 118MB of memory. Sometimes the memory usage increases
dramatically. We've determined that the increases in memory usage
occurs when specific reports are run. When these specific reports are
run the memory usage will increase to over 1GB.
My question is this; after these reports (actions) are finished, the
memory is never released. The mongrel continues to hold over 1GB of
memory, even though the large request is over and done. I first
thought there was a problem in our actions and we needed to do
something to fix it to release the memory. Since then I've noticed
that when any of the mongrels increase their memory usage (even a
little bit) the memory usage NEVER goes down. We have to restart the
mongrels for it to release the memory.
Is this normal? Is mongrel just greedy? Does it never release memory
once it's allocated? Or is this a sign that something is not right in
my app? -
Mike Ball started following the idea "new relic status in your firefox browser" in New Relic.
-
Mike Ball started following the idea "Free Silver Account for Open Source Projects" in New Relic.
-
Mike Ball shared an idea in New Relic on February 12, 2009 22:56:
List each mongrel instance even if you define new applications.When we first started using RPM it listed each individual mongrel instance on the main page, with the stats for that instance. After I defined some applications it no longer lists the stats for each individual mongrel instance.
I really want to see information on each mongrel as well as my defined applications. In order to accomplish this I had to define an application that only contained one mongrel instance. Eight times.
I'd recommend your main pages listed all the apps at the top, the hosts, and then each individual mongrel instance on the bottom. -
Mike Ball shared an idea in New Relic on February 12, 2009 22:50:
Add alternating row color to the main list of Apps/Hosts.We have 11 Apps listed on the main page of RPM and it's difficult to follow the stats for each App. I'd recommend adding alternating row background colors, or something like that.
And no, we don't need that many Apps listed, but I'll address the reason for that in another idea.
Thanks for a great product! -
Mike Ball asked a question in New Relic on February 12, 2009 21:40:
How do I use filter_parameters with params capturing?The newrelic config file says this "# When true, the RoR filter_parameters mechanism is used so that sensitive parameters are not recorded".
The Rails API doesn't mention a filter_parameters mechanism. It has a filter_parameter_logging method. Is that what I'm supposed to use?
Can you please share a code example of how I would block certain HTTP parameters from being sent to New Relic for Errors and/or slow requests.
