August 23

New Relic

Account Setup

  1. 1.
    Create a new account on New Relic and verify your email.
    New Relic: Account Creation
    New Relic Home Page
  2. 2.
    Click on your Profile and navigate to "API keys".
    API Keys
  3. 3.
    Click on "Create a key"
    Create a key
  4. 4.
    Select "Ingest - Licence" for the Key Type and enter in details for the "Name" and "Notes"
    Ingest - License - Key Creation
  5. 5.
    Confirm Licence has been created
    Licence Created
  6. 6.
    Copy the key from the new "Ingest - Licence" and create a variable in your pipeline labeled "SFPOWERSCRIPTS_NEWRELIC_API_KEY" and assign the value of the key. Ensure to mask this value.
    Sample GitLab Variable for New Relic API Key
  7. 7.
    Add another additional variable named "SFPOWERSCRIPTS_NEWRELIC" and set the value to "true".
  8. 8.
    Retrieve your "Account ID" under Profile > Administration > Access Management > Accounts
  9. 9.
    Update the cicd-dashboard.json file in dashboards/NewRelic folder with the value of the "Account id" for all instances of <your-account-id>in the file. Ensure to include the quotation marks for the "Account id". (eg. "1234567")
  10. 10.
    Trigger the scheduled job for "schedule-report-so-pool" job and confirm success.
Avoid checking in the updated "Account id" file directly in your repository if you want to keep this as a secret. This is only needed to import into the Dashboard in the next section.

Dashboard View

  1. 1.
    Navigate to the Dashboard and click on "Import Dashboard".
    Import Dashboard
  2. 2.
    Copy and paste the edited contents of the "cicd-dashboard.json" file in the previous section with the updated "Account id".
    JSON Import Dashboard
  3. 3.
    Click on "Import dashboard"
  4. 4.
    Confirm the "Salesforce CI/CD Dashboard" is created.
  5. 5.
    Click to view details for the "Salesforce CI/CD Dashboard"
Metrics are meant to be reviewed and monitored to ensure the success of your CI/CD setup. Ensure that the team is reviewing the dashboard frequently and identify issues across Scratch Org Creations, Deployments,