New Relic and Lucee

Hi All,

Has anyone used New Relic with Lucee (or Railo in the past). I’ve installed
it and have data coming through on the APM section however I’m not sure I
see how it is particularly useful beyond some very basic metrics, which
while nice are not all that helpful. For example, I go to the “errors”
section and it tells me there have been X errors in the last X hours. It
groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server
Error”, which itself is surely an “HTTP Server Error 500” as that is what
the 500 code means. I click through to the details and all it tells me is
basically the same thing, with the addition of the thread name (which is
frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like, brilliant, I
can see all the queries grouped by the table it is selecting from and
ordered by average time, but again once you drill down you can see the
“Slow queries” but all the values are question marks (?) because you have
parameterised them in your query so all you get is a long list of the same
query over and over taking different amounts of time but no way to
reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some configuration
option or something. I feel it must be the latter so wanted to see what
others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR and
an FR user on other projects but this particular time I’ve been given New
Relic to use and wanted to make sure I wasn’t missing something before
going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member

I blogged about what we did with New Relic and CFML (Railo). See if this helps:

http://corfield.org/blog/post.cfm/new-relic-and-cfml http://corfield.org/blog/post.cfm/new-relic-and-cfml

FWIW, we got more mileage out of instrumenting the Clojure code we call from CFML so we could affect the transaction traces by adding (Java) annotations to calls in our Clojure code:

http://corfield.org/blog/post.cfm/instrumenting-clojure-for-new-relic-monitoring http://corfield.org/blog/post.cfm/instrumenting-clojure-for-new-relic-monitoring

SeanOn Mar 14, 2015, at 3:26 PM, Andrew Dixon <@Andrew_Dixon> wrote:

Has anyone used New Relic with Lucee (or Railo in the past). I’ve installed it and have data coming through on the APM section however I’m not sure I see how it is particularly useful beyond some very basic metrics, which while nice are not all that helpful. For example, I go to the “errors” section and it tells me there have been X errors in the last X hours. It groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server Error”, which itself is surely an “HTTP Server Error 500” as that is what the 500 code means. I click through to the details and all it tells me is basically the same thing, with the addition of the thread name (which is frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like, brilliant, I can see all the queries grouped by the table it is selecting from and ordered by average time, but again once you drill down you can see the “Slow queries” but all the values are question marks (?) because you have parameterised them in your query so all you get is a long list of the same query over and over taking different amounts of time but no way to reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some configuration option or something. I feel it must be the latter so wanted to see what others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR and an FR user on other projects but this particular time I’ve been given New Relic to use and wanted to make sure I wasn’t missing something before going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net/ - Lucee http://lucee.org/ - Member

The issue with the queries not showing detail I believe is a NewRelic
config option (check your newrelic.yml file or whatever). It lets you
decide how much you want to share into the cloud (ie masked data).On Sunday, March 15, 2015 at 9:26:46 AM UTC+11, Andrew Dixon wrote:

Hi All,

Has anyone used New Relic with Lucee (or Railo in the past). I’ve
installed it and have data coming through on the APM section however I’m
not sure I see how it is particularly useful beyond some very basic
metrics, which while nice are not all that helpful. For example, I go to
the “errors” section and it tells me there have been X errors in the last X
hours. It groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server
Error”, which itself is surely an “HTTP Server Error 500” as that is what
the 500 code means. I click through to the details and all it tells me is
basically the same thing, with the addition of the thread name (which is
frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like, brilliant,
I can see all the queries grouped by the table it is selecting from and
ordered by average time, but again once you drill down you can see the
“Slow queries” but all the values are question marks (?) because you have
parameterised them in your query so all you get is a long list of the same
query over and over taking different amounts of time but no way to
reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some configuration
option or something. I feel it must be the latter so wanted to see what
others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR
and an FR user on other projects but this particular time I’ve been given
New Relic to use and wanted to make sure I wasn’t missing something before
going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member

Thanks for this guys, I’ve been playing around with this tonight and it’s
looking good, far better than I was getting with just the basic install.
I’ve pulled together a CFC so I will put together some usage notes and
stick it up on Github for all. Will post a link back once it is up.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - MemberOn 17 March 2015 at 00:09, Phil Sweeney <@Phil> wrote:

The issue with the queries not showing detail I believe is a NewRelic
config option (check your newrelic.yml file or whatever). It lets you
decide how much you want to share into the cloud (ie masked data).

On Sunday, March 15, 2015 at 9:26:46 AM UTC+11, Andrew Dixon wrote:

Hi All,

Has anyone used New Relic with Lucee (or Railo in the past). I’ve
installed it and have data coming through on the APM section however I’m
not sure I see how it is particularly useful beyond some very basic
metrics, which while nice are not all that helpful. For example, I go to
the “errors” section and it tells me there have been X errors in the last X
hours. It groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server
Error”, which itself is surely an “HTTP Server Error 500” as that is what
the 500 code means. I click through to the details and all it tells me is
basically the same thing, with the addition of the thread name (which is
frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like, brilliant,
I can see all the queries grouped by the table it is selecting from and
ordered by average time, but again once you drill down you can see the
“Slow queries” but all the values are question marks (?) because you have
parameterised them in your query so all you get is a long list of the same
query over and over taking different amounts of time but no way to
reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some configuration
option or something. I feel it must be the latter so wanted to see what
others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR
and an FR user on other projects but this particular time I’ve been given
New Relic to use and wanted to make sure I wasn’t missing something before
going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/800e228e-53c9-4764-aac9-98fa3ee68107%40googlegroups.com
https://groups.google.com/d/msgid/lucee/800e228e-53c9-4764-aac9-98fa3ee68107%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

Hi All,

If anyone is interested I’ve now put my component up on Github:

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - MemberOn 19 March 2015 at 23:43, Andrew Dixon <@Andrew_Dixon> wrote:

Thanks for this guys, I’ve been playing around with this tonight and it’s
looking good, far better than I was getting with just the basic install.
I’ve pulled together a CFC so I will put together some usage notes and
stick it up on Github for all. Will post a link back once it is up.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member

On 17 March 2015 at 00:09, Phil Sweeney <@Phil> wrote:

The issue with the queries not showing detail I believe is a NewRelic
config option (check your newrelic.yml file or whatever). It lets you
decide how much you want to share into the cloud (ie masked data).

On Sunday, March 15, 2015 at 9:26:46 AM UTC+11, Andrew Dixon wrote:

Hi All,

Has anyone used New Relic with Lucee (or Railo in the past). I’ve
installed it and have data coming through on the APM section however I’m
not sure I see how it is particularly useful beyond some very basic
metrics, which while nice are not all that helpful. For example, I go to
the “errors” section and it tells me there have been X errors in the last X
hours. It groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server
Error”, which itself is surely an “HTTP Server Error 500” as that is what
the 500 code means. I click through to the details and all it tells me is
basically the same thing, with the addition of the thread name (which is
frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like,
brilliant, I can see all the queries grouped by the table it is selecting
from and ordered by average time, but again once you drill down you can see
the “Slow queries” but all the values are question marks (?) because you
have parameterised them in your query so all you get is a long list of the
same query over and over taking different amounts of time but no way to
reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some
configuration option or something. I feel it must be the latter so wanted
to see what others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR
and an FR user on other projects but this particular time I’ve been given
New Relic to use and wanted to make sure I wasn’t missing something before
going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/800e228e-53c9-4764-aac9-98fa3ee68107%40googlegroups.com
https://groups.google.com/d/msgid/lucee/800e228e-53c9-4764-aac9-98fa3ee68107%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

Check out https://dripstat.com
kind of a new relic clone, but more affordable.

we have been using it on our old railo servers.
putting it on our lucee servers now.On Saturday, March 14, 2015 at 5:26:46 PM UTC-5, Andrew Dixon wrote:

Hi All,

Has anyone used New Relic with Lucee (or Railo in the past). I’ve
installed it and have data coming through on the APM section however I’m
not sure I see how it is particularly useful beyond some very basic
metrics, which while nice are not all that helpful. For example, I go to
the “errors” section and it tells me there have been X errors in the last X
hours. It groups these errors together as something like:

HttpServerError 500 4
Internal Server Error 1

Ok, so there have been 4 “HTTP Server Error 500” and 1 “Internal Server
Error”, which itself is surely an “HTTP Server Error 500” as that is what
the 500 code means. I click through to the details and all it tells me is
basically the same thing, with the addition of the thread name (which is
frankly useless), the URL and the referrer. Nothing else helpful at all.

Another example is the Databases section. At first I was like, brilliant,
I can see all the queries grouped by the table it is selecting from and
ordered by average time, but again once you drill down you can see the
“Slow queries” but all the values are question marks (?) because you have
parameterised them in your query so all you get is a long list of the same
query over and over taking different amounts of time but no way to
reproduce because you don’t have the actual values.

Either it is next to useless or I’m missing something, some configuration
option or something. I feel it must be the latter so wanted to see what
others thought.

BTW, before you suggest Fusion Reactor instead, I’m already aware of FR
and an FR user on other projects but this particular time I’ve been given
New Relic to use and wanted to make sure I wasn’t missing something before
going back and saying I need FR instead.

Thanks.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon
mso http://www.mso.net - Lucee http://lucee.org - Member

New Relic have a free tier as well.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.orgOn 16 June 2015 at 09:02, Tom Chiverton <@Tom_Chiverton> wrote:

On Monday, June 15, 2015 at 3:55:08 PM UTC+1, ronnie otts wrote:

Check out https://dripstat.com
kind of a new relic clone, but more affordable.

we have been using it on our old railo servers.
putting it on our lucee servers now.

Crikey - a free tier for unlimited hosts… I wonder if the FusionReactor
folks know !

Tom


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/fb6e742c-5db7-4569-b389-e36c0faf3255%40googlegroups.com
https://groups.google.com/d/msgid/lucee/fb6e742c-5db7-4569-b389-e36c0faf3255%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

Crikey - a free tier for unlimited hosts… I wonder if the FusionReactor
folks know !

TomOn Monday, June 15, 2015 at 3:55:08 PM UTC+1, ronnie otts wrote:

Check out https://dripstat.com
kind of a new relic clone, but more affordable.

we have been using it on our old railo servers.
putting it on our lucee servers now.

We have added official support for Lucee monitoring in DripStat
http://blog.dripstat.com/apache-lucee-monitoring-with-dripstat/

We offer similar functionality to NewRelic.

Our native integration with Lucee means you can install and start using it
within just a couple minutes.
We will also be keeping our integration updated as versions of Lucee
continue to evolve.

PrashantOn Tuesday, June 16, 2015 at 3:29:57 AM UTC-7, Andrew Dixon wrote:

New Relic have a free tier as well.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.org

On 16 June 2015 at 09:02, Tom Chiverton <tom.ch...@gmail.com <javascript:> wrote:

On Monday, June 15, 2015 at 3:55:08 PM UTC+1, ronnie otts wrote:

Check out https://dripstat.com
kind of a new relic clone, but more affordable.

we have been using it on our old railo servers.
putting it on our lucee servers now.

Crikey - a free tier for unlimited hosts… I wonder if the FusionReactor
folks know !

Tom


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+un...@googlegroups.com <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/fb6e742c-5db7-4569-b389-e36c0faf3255%40googlegroups.com
https://groups.google.com/d/msgid/lucee/fb6e742c-5db7-4569-b389-e36c0faf3255%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.