Install and configure OCI log forwarding

Runs Oracle Resource Manager stacks to provision what the integration needs, instead of you creating each piece by hand in the OCI console. Follow the on-screen instructions to establish the connection.

In the OCI console create the required policies and service connectors. The guided installation walks you through these steps in order: create a compartment, create a dynamic group, set up a key vault secret, create a policy, set up a network, set up the logs function, set up an audit logs connector (optional), set up the logs connector, set up WIF, and create the connection.

You will need the following information to complete the process:

• Name the dedicated compartment as newrelic_compartment_DO_NOT_REMOVE. Create it in your OCI home region.
• While creating the dynamic group in the root compartment under the default domain, add the rules resource.type = 'serviceconnector' and resource.type = 'fnfunc'.
• Create a key vault to securely store your New Relic license key and user key for authentication.
  
  1. Create a key vault. In the OCI console, locate and access the Key Management and Vault services and create a vault in the compartment you created earlier, naming it (for example, newrelic-vault) and choosing a standard or virtual private vault based on your security requirements.
     
  2. Create a master encryption key. In the vault, create a master key named (for example) newrelic-encryption-key, using the AES algorithm and a 256-bit key length.
     
  3. Create secrets for your API keys. Create a secret for your New Relic ingest license key, named (for example) newrelic-ingest-key, selecting the master key you just created and pasting your ingest license key as the secret content (Plain Text). Repeat to create a second secret for your New Relic user key, named (for example) newrelic-user-key, pasting your user key as the secret content (Plain Text).
• Create a serverless application and deploy the New Relic function that processes and forwards your OCI logs.
  
  1. Create a serverless application for logging
     • Access the Functions service under Developer Services in the OCI console.
     • Create a new application with this configuration:
       • Name: a descriptive name (for example, newrelic-logging-function-app)
       • Compartment: your designated New Relic compartment
       • VCN: the VCN created for the New Relic integration
       • Subnet: the private subnet, for secure connectivity
       • Shape: GENERIC_X86, for the application shape
     • Save the application configuration.
  2. Configure environment variables for logging
     • Within the application settings, go to the configuration section and add these variables:
       • VAULT_REGION: the region where you created your key vault
       • DEBUG_ENABLED: false for production use (or true for debugging)
       • NEW_RELIC_REGION: your New Relic region (US, EU, or JP)
       • SECRET_OCID: the OCID of your New Relic license key secret from the key vault
       • CLIENT_TTL: 30 seconds, for the license key refresh interval
     • Optionally, to enable self-observability metrics on the log forwarder, also add
       • FORWARDER_METRICS_TIER: Controls which self-observability metrics the forwarder emits. Defaults to basic. Refer to the metric tiers for what each setting collects.
       • TENANCY_NAME: Identifies your OCI tenancy by its display name, tagging the forwarder's metrics so you can tell tenancies apart if you monitor more than one.
       • COMPARTMENT_NAME: Identifies, by display name, the compartment where you deployed the logs function, tagging metrics for per-compartment breakdowns. If you deployed into the tenancy's root compartment, use the same value as TENANCY_NAME.
     • Once you enable forwarder metrics, import the observability dashboard to visualize them.
     • Save the configuration variables.
  3. Deploy the logging function
     • Create a new function within the application with these specifications:
       • Function name: a descriptive name (for example, newrelic-logging-function)
       • Image source: the New Relic logging Docker image, which you copy into a private repository in your Container Registry
       • Memory allocation: at least 128 MB
       • Timeout: 300 seconds, for adequate processing time
     • For the Docker image, pull a specific version of the New Relic log-forwarder image from Docker Hub (not :latest — check Docker Hub's tags page for the current version) and push it into your own Container Registry under that same version tag.
     • Tag and push the image to a private repository in your namespace in the same region as the function, and reference it in your function configuration.
     • Complete the function creation and deployment process.
     • To upgrade later, push the new image again and update the function to use it.
  4. (Optional) Enable function logging
     • Access the monitoring settings for your function application.
     • Enable function invocation logs by selecting or creating an appropriate log group, configuring log retention and access policies, and activating log collection for the function.
     • For more information, see the Oracle documentation on exporting function log files.

Terraform is the recommended setup method for logs.
For the detailed integration steps, refer to the OCI cloud integration guide.