Forwarding logs to New Relic
This guide describes how to configure your App Builder application to forward application logs to your New Relic deployment.
Prerequisites
A New Relic account and an Ingest license API key.
A local development setup for your App Builder application.
The latest version of Adobe I/O CLI. Check your version by running
aio --version
. Runnpm install -g @adobe/aio-cli
to update.
Identify the API key and base URI
Log in to New Relic and navigate to the API keys screen. Pick the
INGEST - LICENSE
API key type you want to use and copy thekey
value for later use.Depending on the region hosting your New Relic account, you must use the United States or European endpoint as a
base uri
. If you don't know the region of your New Relic instance, check the browser URL of your New Relic home. If the URL begins withhttps://one.newrelic.com/
, specifyhttps://log-api.newrelic.com/log/v1
as the URI. If the URL begins withhttps://one.eu.newrelic.com/
, specifyhttps://log-api.eu.newrelic.com/log/v1
.
Set up Log Forwarding in App Builder
From the command line, navigate to the App Builder project directory on your machine.
Run the following command and supply the values from previous steps.
Copied to your clipboardaio app config set log-forwarding? select log forwarding destination: New Relic? base URI: <base_uri>? license key: <license_key>The URI value must include the protocol (
https://
).Verify that the config change has taken effect.
Copied to your clipboardaio app config get log-forwardingExecute an action in your App Builder application workspace to generate logs.
Go to New Relic Home > Logs and run your query.
If you don't see any logs in New Relic, check the log forwarding errors.
Copied to your clipboardaio app config get log-forwarding errors
If you are unable to set up log forwarding, visit the App Builder forums for support.