New Relic support for reps-dev.allizom.org

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: nemo-yiannis, Assigned: cliang)

Tracking

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1298] , URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
We are having an issue with New Relic and our dev instance for ReMo (reps-dev.allizom.org). It shows a flat web transaction chart from July 28 2014 until today. This cannot be true since we have plenty of errors triggered from automated tests.

It seems like reps-dev.allizom.org is not reporting any data to New Relic. Can you help us with that?

Thank you

Updated

4 years ago
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1298]
(Reporter)

Updated

4 years ago
Blocks: 1068090
OS: Linux → All
Hardware: x86_64 → All
(Assignee)

Updated

4 years ago
Assignee: server-ops-webops → cliang
(Assignee)

Comment 1

4 years ago
Can you please verify that reporting is now working as expected?  (I was able to generate some web traffic and see it appear on both the Monitoring -> Overview and Monitoring -> Transactions tabs.  )

I think reporting to New Relic stopped working because one or more of the New Relic related RPMs was updated but the corresponding configuration was not updated at the same time.  They should now be sorted out.  

For future reference, since there had been updates already, I pushed everything to the latest working combination:
   newrelic-daemon (4.13.1.71)
   newrelic-php5 (4.13.1.71)
   newrelic-php5-common (4.13.1.71)
   python-newrelic (2.32.0.28)
(In reply to C. Liang [:cyliang] from comment #1)
> Can you please verify that reporting is now working as expected?  (I was
> able to generate some web traffic and see it appear on both the Monitoring
> -> Overview and Monitoring -> Transactions tabs.  )
> 
> I think reporting to New Relic stopped working because one or more of the
> New Relic related RPMs was updated but the corresponding configuration was
> not updated at the same time.  They should now be sorted out.  
> 
> For future reference, since there had been updates already, I pushed
> everything to the latest working combination:
>    newrelic-daemon (4.13.1.71)
>    newrelic-php5 (4.13.1.71)
>    newrelic-php5-common (4.13.1.71)
>    python-newrelic (2.32.0.28)

I don't see the Python stacktrace/exception that I triggered, from bug 1069782, on https://rpm.newrelic.com/accounts/263620/applications/3650909/traced_errors
(Assignee)

Comment 3

4 years ago
@stephend: Can you tell me what you expected to see?  (If you have an example link from the reps.mozilla.org site, that would be very helpful.)

For what it's worth, I was able to see the error in the stacktrace reflected in:
   https://rpm.newrelic.com/accounts/263620/applications/3650909/externals#id=505300679
(In reply to C. Liang [:cyliang] from comment #3)
> @stephend: Can you tell me what you expected to see?  (If you have an
> example link from the reps.mozilla.org site, that would be very helpful.)
> 
> For what it's worth, I was able to see the error in the stacktrace reflected
> in:
>   
> https://rpm.newrelic.com/accounts/263620/applications/3650909/
> externals#id=505300679

It's working now -- last night, it wasn't in near-real time, like it was just now (see screenshot).

This looks fixed to me, for dev; thanks!
Created attachment 8497611 [details]
reps-new-relic.png
(Assignee)

Comment 6

4 years ago
I'm not sure what the normal lag time is for pushing data to New Relic.  Let me know if you find it consistently being "laggy".
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.