search

newrelic / nr1-learn-nrql

NR1 learn NRQL helps New Relic Customers quickly learn our custom query language - NRQL
Apache License 2.0
20 stars 15 forks source link

Using Fallback Public_APICall event instead of Transaction even the account has Transaction events. #54

Open csalvador-nr opened 11 months ago

csalvador-nr commented 11 months ago

Description

I have found that after enabling the app on my account, in order for data to appear on the queries I have to select the account in the top dropdown selector from all the accounts I have access to. This means that users with access to only 1 account or organisations with only 1 account, where the dropdown selector does not appear, the queries are not updated and appear to query the Public_APICall event, even though I have Transaction events.

Steps to Reproduce

Enable NRQL Lessons throughout the UI in one single-account organisation.

Expected Behaviour

It should use Transaction events automatically or that the account does not need to be selected in the selector to refresh to display data.

Your Environment

Additional context

SCR-20231006-otkg

jsbnr commented 11 months ago

Thanks for reporting, it should work with one account. I'll eyeball in the next release.

shavounet commented 7 months ago

~Hi, I have the same issue with a multi-account user. There is no dropdown and I only have Public_APICall even though Transactions are enabled on one account.~

~I also tried with a single-account user that have Transactions, without success.~

EDIT: playing with app permission I could display the dropdown (~but it disappeared after a while~ not sure what happened... I can switch it now). Changing the value did correctly update the examples. But most people in my organization only have access to one account and cannot use this trick.

I'm no JS (even less React) expert, but is this ok if the call is calling async method without awaiting them ?