Skip to content

NewRelic

Parameters

  • apiURL - the api server url, e.g. https://api.newrelic.com
  • apiKey - a NewRelic ApiKey

Configuration

  1. Create a NewRelic Api Key
  2. Store apiKey in argo-rollouts-notification-secret Secret and configure NewRelic integration in argo-rollouts-notification-configmap ConfigMap
apiVersion: v1
kind: ConfigMap
metadata:
  name: argo-rollouts-notification-configmap
data:
  service.newrelic: |
    apiURL: <api-url>
    apiKey: $newrelic-apiKey

apiVersion: v1
kind: Secret
metadata:
  name: <secret-name>
stringData:
  newrelic-apiKey: apiKey
  1. Copy Application ID
  2. Create subscription for your NewRelic integration
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.argoproj.io/subscribe.<trigger-name>.newrelic: <app-id>

Templates

  • description - optional, high-level description of this deployment, visible in the Summary page and on the Deployments page when you select an individual deployment.
  • Defaults to message
  • changelog - optional, A summary of what changed in this deployment, visible in the Deployments page when you select (selected deployment) > Change log.
  • Defaults to {{(call .repo.GetCommitMetadata .app.status.sync.revision).Message}}
  • user - optional, A username to associate with the deployment, visible in the Summary and on the Deployments.
  • Defaults to {{(call .repo.GetCommitMetadata .app.status.sync.revision).Author}}
context: |
  argocdUrl: https://example.com/argocd

template.app-deployed: |
  message: Application {{.app.metadata.name}} has successfully deployed.
  newrelic:
    description: Application {{.app.metadata.name}} has successfully deployed