Docs » Supported integrations in Splunk Observability Cloud » Cloud Foundry Loggregator Firehose

Cloud Foundry Loggregator Firehose πŸ”—

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the Cloud Foundry Loggregator Firehose monitor type to create a Cloud Foundry Firehose nozzle. The integration connects to the Cloud Foundry Reverse Log Proxy (RLP) Gateway that feeds metrics from the Loggregator. It supports gauge and counter metrics.

This integration is available on Linux.

This integration uses the new RLP Gateway model that was introduced in Pivotal Cloud Foundry (PCF) 2.4, so it doesn’t work with older releases.

Benefits πŸ”—

After you configure the integration, you can access these features:

Installation πŸ”—

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration πŸ”—

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example πŸ”—

To activate this integration, add the following to your Collector configuration:

    type: cloudfoundry-firehose-nozzle
    ... # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

      receivers: [smartagent/cloudfoundry-firehose-nozzle]

Configuration settings πŸ”—

The following table shows the configuration options for this integration:








The base URL to the RLP Gateway server. This is quite often of

the form https://log-stream.<CLOUD CONTROLLER SYSTEM DOMAIN> if using PCF 2.4+.




Whether to skip SSL/TLS verification when using HTTPS to connect

to the RLP Gateway (default: false)




The UAA username for a user that has the appropriate authority

to fetch logs from the Firehose (usually the logs.admin authority)




The password for the above UAA user




The URL to the UAA server. This monitor obtains an access token

from this server that it uses to authenticate with the RLP Gateway.




Whether to skip SSL/TLS verification when using HTTPS to connect

to the UAA server (default: false)




The nozzle’s shard ID. All nozzle instances with the same ID

receive an exclusive subset of the data from the Firehose. The default should suffice in the vast majority of use cases. (default: signalfx_nozzle)

PCF configuration πŸ”—

Most of PCF Key Performance Indicators (KPIs) come through the Firehose. Refer to PCF documentation for more information on KPIs to determine when to scale up or down your cluster.

To create Cloud Foundry User Account and Authentication (UAA) user with the proper permissions to access the RLP Gateway, run the following command:

$ uaac client add my-v2-nozzle \
    --name signalfx-nozzle \
    --secret <signalfx-nozzle client secret> \
    --authorized_grant_types client_credentials,refresh_token \
    --authorities logs.admin

Set the uaaUsername config value to signalfx-nozzle and the uaaPassword field to the <signalfx-nozzle client secret> that you select.

Metrics πŸ”—

The gauge and counter metrics are collected from PCF Platform apps and platform components in the following way:

  • Firehose gauge metrics are converted to Splunk Infrastructure Monitoring gauges.

  • Firehose counter metrics are converted to Infrastructure Monitoring cumulative counters metrics.

  • All of the tags in the Firehose envelopes are converted to dimensions when sending to Infrastructure Monitoring.

The following metrics are available for this integration:

Notes πŸ”—

  • To learn more about the available in Observability Cloud see Metric types

  • In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.

  • In MTS-based subscription plans, all metrics are custom.

  • To add additional metrics, see how to configure extraMetrics in Add additional metrics

## Troubleshooting

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Available to prospective customers and free trial users

  • Ask a question and get answers through community support at Splunk Answers .

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success .