> ## Documentation Index
> Fetch the complete documentation index at: https://otel.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# Faro

> OpenTelemetry receiver for Faro

# Faro Receiver

![Status](https://img.shields.io/badge/status-alpha-red)

**Available in:** `contrib`

**Maintainers:** [@dehaansa](https://github.com/dehaansa), [@rlankfo](https://github.com/rlankfo), [@mar4uk](https://github.com/mar4uk)

**Source:** [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/faroreceiver)

## Supported Telemetry

![Logs](https://img.shields.io/badge/logs-alpha-blue) ![Traces](https://img.shields.io/badge/traces-alpha-orange)

## Overview

## Receiver Configuration

Faro follows the [confighttp] configuration, some examples are shown below

### Example Configuration

```yaml theme={null}
receivers:
  faro:
    endpoint: 'localhost:8081'
```

### Advanced Configuration

```yaml theme={null}
receivers:
  faro:
    endpoint: 'localhost:8081'
    cors:
      allowed_origins: "*"
```

[confighttp]: https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/confighttp#server-configuration

## Configuration

### Example Configuration

```yaml theme={null}
endpoint: localhost:8080
  # The following entry demonstrates how to specify TLS credentials for the server.
  # Note: These files do not exist. If the receiver is started with this configuration, it will fail.
tls:
  cert_file: test.crt
  key_file: test.key

# The following entry demonstrates how to configure the Faro receiver to allow Cross-Origin Resource Sharing (CORS).
# Both fully qualified domain names and the use of wildcards are supported.
cors:
  allowed_origins:
    - https://*.test.com # Wildcard subdomain. Allows domains like https://www.test.com and https://foo.test.com but not https://wwwtest.com.
    - https://test.com # Fully qualified domain name. Allows https://test.com only.
  max_age: 7200
```

***

*Last generated: 2026-07-06*