If the pageUrl and the requestUrl have different domains, then this is a cross-origin request, Redeploy No Traces Appearing To check if a specific request is cross-origin, specify the ‘requestUrl’ in your query SELECT count(*) FROM AjaxRequest WHERE appName like ''ĪND requestUrl = '' LIMIT 100 FACET pageUrl SELECT count(*) FROM AjaxRequest WHERE appName like '' If the request you want to be traced starts on one domain and goes to an endpoint on a different domain, it’s a cross-origin request and you need to enable CORS sharing in order for Browser Distributed Tracing to generate traces for them. Optional - Enable cross-origin resource sharing (CORS).Go to your Browser application ‘Settings’ to ‘Application settings’ and turn on the Distributed tracing toggle.Check your Browser Agent meets the requirements.(Owners, Admins and Add-On manager Users only) Go to the ‘Agent Initialization’ and search for the configuration setting for Distributed Tracing to confirm it is enabled.Confirm the agent version is correct and meets the minimum requirements.
When you run the query, the Blameless Validation engine will throw the following error message because of the use more than one column value in the query:Īpm. Started Enabling Distributed Tracing for APM AgentsĬonfirm that your agent meets the minimum requirements Query: SELECT average(.utilization ), average( ) FROM Metric WHERE appName LIKE '%' When you run the query, the Blameless Validation engine will throw the following error message because of the use of the “TIMESERIES” keyword:Įrror: Please do not include TIMESERIES clause, we'll add it when querying data Example: Error using more than on column Query: SELECT average(.utilization ) FROM Metric WHERE appName LIKE '%' TIMESERIES When you run the query, the Blameless Validation engine will throw the following error message:Įrror: NRQL Syntax Error: Error at line 1 position 108, unexpected 'SINCE': error while querying metrics from New Relic Example: Error using the “TIMESERIES” keyword Query: SELECT average(.utilization ) FROM Metric WHERE appName LIKE '%' SINCE 30 MINUTES Refer to the following examples: Example: Error using the “SINCE” keyword We have a validation function for avoiding bad user experience. The query shouldn’t contain the keywords “SINCE” and “TIMESERIES” as we add them from the Blameless side. If the query is valid and satisfies the requirements, you should see a green checkmark. SELECT average(.utilization ) FROM Metric WHERE appName LIKE '%' If you choose “Saturation”, select the following example: If you choose “Throughput”, select the following example::ĭ. If you choose “Latency”, select the following example:Ĭ. Good metric: SELECT count(*)-sum(error) FROM Transaction Valid metric: SELECT count(*) FROM Transactionī. If you choose “Availability”, select the following metric examples: Complete the steps to create the SLO and click the “Save” button.Ī.Copy and paste the desired metric in the required field. Click on the “New Relic” button under the Select Data Source label to choose “New Relic” "as the datasource.Create and define an SLO in the Blameless web application.Select the SLO portal icon (target) on the Blameless web application navigation menu.
To test and confirm the integration, you need to have at least one service created within the Service Registry (instructions on how to appear in the previous section). SLIs created in Blameless’ SLO Manager, and fed from New Relic metrics are built using the New Relic Query Language (NRQL)-allowing a broad and flexible support for the versatile New Relic metric types (APM, Synthetics, etc.), across all SLI types (Availability, Latency, Throughput, and Saturation).
Open or switch windows to the Blameless application.Click on "Show" and copy the REST API key provided.Select "API Keys" under the Integrations section on the left nav bar.Select "Account Settings" in the upper right corner of the New Relic Home Page.When you create the New Relic API key, the key needs to be a User key.