Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Using attributes from two different tables


#1

Hi,

I saw this NRQL in a post and I woulid to check if it really works. For me is new the idea to use two attributes from different tables.

Can any one confirm is it really works?

SELECT apdex(PageView.duration, 5.0) as ‘Browser Apdex’, apdex(Transaction.duration, 1.0 ) as ‘Backend Apdex’ from PageView, Transaction since 24 hours ago timeseries AUTO


#2

Hi @Renato.Malvino - Aside from changing the quotes around the alias text, I got this to run by a straight copy and paste into Insights.


#3

Similar to Stefan, in my testing this worked fine - but I have never seen Transaction.duration as a way to target specifically Transactions duration attribute when querying multiple event types.

I’ve asked some teams internally if this is new, or if this is an actually supported & accurate way to target what it is you are trying to target. I’ll follow up when I hear back. But for now, since this appears to work ok, I imagine this is totally fine to keep using.


#4

The update I have is that EventName.Attribute is accurate, and totally fine to use, it’s just not well known (internally too since I hadn’t heard of it).


#5

It would be great to have the documentation updated to reflect this, assuming it works for all event types :wink:


#6

I’m not sure where best this lives in the docs - but I’ll ask the team to get it added.