Configuring Collectors

sfp supports multiple metrics collectors to send build, deploy, validate, and release metrics to your observability platform of choice.

Available Collectors

CollectorDescription
sfp ServerBuilt-in Victoria Metrics with query CLI
DatadogNative integration with Datadog
SplunkNative integration with Splunk
New RelicNative integration with New Relic
StatsDForward to any StatsD-compatible collector

Multiple Collectors

sfp can send metrics to multiple collectors simultaneously. Simply configure the environment variables for each collector you want to use:

# Send metrics to both sfp server and Datadog
export SFP_SERVER_URL=http://your-sfp-server:3029
export SFPOWERSCRIPTS_DATADOG=true
export SFPOWERSCRIPTS_DATADOG_API_KEY=your-api-key

sfp build  # Metrics sent to both destinations

Default Behavior

sfp Server (Default)

When SFP_SERVER_URL is configured, all sfp commands automatically emit metrics to the sfp server. No additional configuration is required - simply set the server URL and authenticate:

sfp config set server-url http://your-sfp-server:3029
sfp config set server-email your-email@example.com
sfp server auth login

Once configured, any command (build, deploy, release, validate, etc.) will automatically send metrics to the server.

External Collectors (Datadog, Splunk, New Relic, StatsD)

Use external collectors when you need to:

  • Integrate with an existing observability platform
  • Correlate sfp metrics with other system metrics
  • Use advanced alerting and dashboard features
  • Meet compliance requirements for specific platforms

On this page