Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GEN-1932]: add HyperDX destination support and documentation #2084

Merged
merged 9 commits into from
Dec 29, 2024
87 changes: 43 additions & 44 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,13 +26,13 @@ Odigos is an open-source distributed tracing solution that simplifyes and improv

## Key Features

* **Code-Free Instrumentation** : Set up distributed tracing in minutes, eliminating manual code modifications.
* **Multi-Language Support** : Works with Java, Python, .NET, Node.js, and Go applications.
* **eBPF-Powered** : Utilizes eBPF technology for high-performance instrumentation of Go applications. eBPF-based instrumentation for Java, Python, and Node.js is available in the enterprise edition.
* **OpenTelemetry Compatible** : Generates traces in OpenTelemetry format for broad tool compatibility.
* **Vendor Agnostic** : Integrates with various monitoring solutions, avoiding vendor lock-in.
* **Automatic Scaling** : Manages and scales OpenTelemetry collectors based on data volume.
* **Opinionated Defaults** : Supplies common defaults and best practices out-of-the-box, requiring no deep knowledge of OpenTelemetry.
- **Code-Free Instrumentation** : Set up distributed tracing in minutes, eliminating manual code modifications.
- **Multi-Language Support** : Works with Java, Python, .NET, Node.js, and Go applications.
- **eBPF-Powered** : Utilizes eBPF technology for high-performance instrumentation of Go applications. eBPF-based instrumentation for Java, Python, and Node.js is available in the enterprise edition.
- **OpenTelemetry Compatible** : Generates traces in OpenTelemetry format for broad tool compatibility.
- **Vendor Agnostic** : Integrates with various monitoring solutions, avoiding vendor lock-in.
- **Automatic Scaling** : Manages and scales OpenTelemetry collectors based on data volume.
- **Opinionated Defaults** : Supplies common defaults and best practices out-of-the-box, requiring no deep knowledge of OpenTelemetry.

## Why Choose Odigos

Expand Down Expand Up @@ -85,48 +85,47 @@ For more details, see our [quickstart guide](https://docs.odigos.io/intro).

### Managed Destinations


| Destination | Traces | Metrics | Logs |
| ------------------------- | :------: | :-------: | :----: |
| AppDynamics | ✅ | ✅ | ✅ |
| Axiom | ✅ | | ✅ |
| AWS S3 | ✅ | | ✅ |
| Azure Blob Storage | ✅ | | ✅ |
| Causely | ✅ | | |
| Chronosphere | ✅ | ✅ | |
| Coralogix | ✅ | ✅ | ✅ |
| Datadog | ✅ | ✅ | ✅ |
| Dynatrace | ✅ | ✅ | ✅ |
| Gigapipe | ✅ | | |
| Google Cloud Monitoring | ✅ | ✅ | |
| Google Cloud Storage | ✅ | | ✅ |
| Grafana Cloud | ✅ | ✅ | ✅ |
| Honeycomb | ✅ | ✅ | ✅ |
| Last9 | ✅ | ✅ | |
| Lightstep | ✅ | | |
| Logz.io | ✅ | ✅ | ✅ |
| New Relic | ✅ | ✅ | ✅ |
| OpsVerse | ✅ | ✅ | ✅ |
| Sentry | ✅ | | |
| Splunk | ✅ | | |
| Sumo Logic | ✅ | ✅ | ✅ |
| ----------------------- | :----: | :-----: | :--: |
| AppDynamics | ✅ | ✅ | ✅ |
| Axiom | ✅ | | ✅ |
| AWS S3 | ✅ | | ✅ |
| Azure Blob Storage | ✅ | | ✅ |
| Causely | ✅ | | |
| Chronosphere | ✅ | ✅ | |
| Coralogix | ✅ | ✅ | ✅ |
| Datadog | ✅ | ✅ | ✅ |
| Dynatrace | ✅ | ✅ | ✅ |
| Gigapipe | ✅ | | |
| Google Cloud Monitoring | ✅ | ✅ | |
| Google Cloud Storage | ✅ | | ✅ |
| Grafana Cloud | ✅ | ✅ | ✅ |
| Honeycomb | ✅ | ✅ | ✅ |
| HyperDX | ✅ | ✅ | ✅ |
| Last9 | ✅ | ✅ | |
| Lightstep | ✅ | | |
| Logz.io | ✅ | ✅ | ✅ |
| New Relic | ✅ | ✅ | ✅ |
| OpsVerse | ✅ | ✅ | ✅ |
| Sentry | ✅ | | |
| Splunk | ✅ | | |
| Sumo Logic | ✅ | ✅ | ✅ |

## Self-Hosted (Open Source) Destinations


| Destination | Traces | Metrics | Logs |
| --------------- | :------: | :-------: | :----: |
| ClickHouse | ✅ | ✅ | ✅ |
| Elasticsearch | ✅ | | ✅ |
| Jaeger | ✅ | | |
| Loki | | | ✅ |
| OTLP | ✅ | ✅ | ✅ |
| OTLP HTTP | ✅ | ✅ | ✅ |
| Prometheus | | ✅ | |
| Quickwit | ✅ | | |
| qryn | ✅ | ✅ | ✅ |
| SigNoz | ✅ | ✅ | ✅ |
| Tempo | ✅ | | |
| ------------- | :----: | :-----: | :--: |
| ClickHouse | ✅ | ✅ | ✅ |
| Elasticsearch | ✅ | | ✅ |
| Jaeger | ✅ | | |
| Loki | | | ✅ |
| OTLP | ✅ | ✅ | ✅ |
| OTLP HTTP | ✅ | ✅ | ✅ |
| Prometheus | | ✅ | |
| Quickwit | ✅ | | |
| qryn | ✅ | ✅ | ✅ |
| SigNoz | ✅ | ✅ | ✅ |
| Tempo | ✅ | | |

Can't find the destination you need? Help us by following our quick [add new destination](https://docs.odigos.io/adding-new-dest) guide and submitting a PR.

Expand Down
69 changes: 69 additions & 0 deletions common/config/hyperdx.go
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
package config

import (
"errors"

"github.com/odigos-io/odigos/common"
)

const (
HyperDXEndpoint = "HYPERDX_ENDPOINT"
)

var (
ErrorHyperDXEndpointMissing = errors.New("HyperDX is missing a required field (\"HYPERDX_ENDPOINT\"), HyperDX will not be configured")
)

type HyperDX struct{}

func (j *HyperDX) DestType() common.DestinationType {
return common.HyperDxDestinationType
}

func (j *HyperDX) ModifyConfig(dest ExporterConfigurer, cfg *Config) error {
config := dest.GetConfig()
uniqueUri := "hdx-" + dest.GetID()

url, exists := config[HyperDXEndpoint]
if !exists {
return ErrorHyperDXEndpointMissing
}

endpoint, err := parseOtlpGrpcUrl(url, false)
BenElferink marked this conversation as resolved.
Show resolved Hide resolved
if err != nil {
return err
}

exporterName := "otlp/" + uniqueUri
exporterConfig := GenericMap{
"endpoint": endpoint,
"headers": GenericMap{
"authorization": "${HYPERDX_API_KEY}",
},
}

cfg.Exporters[exporterName] = exporterConfig

if isTracingEnabled(dest) {
pipeName := "traces/" + uniqueUri
cfg.Service.Pipelines[pipeName] = Pipeline{
Exporters: []string{exporterName},
}
}

if isMetricsEnabled(dest) {
pipeName := "metrics/" + uniqueUri
cfg.Service.Pipelines[pipeName] = Pipeline{
Exporters: []string{exporterName},
}
}

if isLoggingEnabled(dest) {
pipeName := "logs/" + uniqueUri
cfg.Service.Pipelines[pipeName] = Pipeline{
Exporters: []string{exporterName},
}
}

return nil
}
12 changes: 6 additions & 6 deletions common/config/root.go
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,12 @@ const (
)

var availableConfigers = []Configer{
&Middleware{}, &AppDynamics{}, &Honeycomb{}, &GrafanaCloudPrometheus{}, &GrafanaCloudTempo{},
&GrafanaCloudLoki{}, &Datadog{}, &NewRelic{}, &Logzio{}, &Last9{}, &Prometheus{},
&Tempo{}, &Loki{}, &Jaeger{}, &GenericOTLP{}, &OTLPHttp{}, &Elasticsearch{}, &Quickwit{}, &Signoz{}, &Qryn{},
&OpsVerse{}, &Splunk{}, &Lightstep{}, &GoogleCloud{}, &GoogleCloudStorage{}, &Sentry{}, &AzureBlobStorage{},
&AWSS3{}, &Dynatrace{}, &Chronosphere{}, &ElasticAPM{}, &Axiom{}, &SumoLogic{}, &Coralogix{}, &Clickhouse{},
&Causely{}, &Uptrace{}, &Debug{}, &QrynOSS{}, &Nop{}, &Mock{},
&AppDynamics{}, &Axiom{}, &AWSS3{}, &AzureBlobStorage{}, &Causely{}, &Chronosphere{}, &Clickhouse{}, &Coralogix{},
&Datadog{}, &Debug{}, &Dynatrace{}, &ElasticAPM{}, &Elasticsearch{}, &GenericOTLP{}, &GoogleCloud{},
&GoogleCloudStorage{}, &GrafanaCloudLoki{}, &GrafanaCloudPrometheus{}, &GrafanaCloudTempo{},
&Honeycomb{}, &HyperDX{}, &Jaeger{}, &Last9{}, &Lightstep{}, &Logzio{}, &Loki{}, &Middleware{}, &Mock{}, &NewRelic{},
&Nop{}, &OpsVerse{}, &OTLPHttp{}, &Prometheus{}, &Qryn{}, &QrynOSS{}, &Quickwit{}, &Sentry{},
&Signoz{}, &Splunk{}, &SumoLogic{}, &Tempo{}, &Uptrace{},
}

type Configer interface {
Expand Down
1 change: 1 addition & 0 deletions common/dests.go
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ const (
GrafanaCloudPrometheusDestinationType DestinationType = "grafanacloudprometheus"
GrafanaCloudTempoDestinationType DestinationType = "grafanacloudtempo"
HoneycombDestinationType DestinationType = "honeycomb"
HyperDxDestinationType DestinationType = "hyperdx"
JaegerDestinationType DestinationType = "jaeger"
Last9DestinationType DestinationType = "last9"
LightstepDestinationType DestinationType = "lightstep"
Expand Down
30 changes: 30 additions & 0 deletions destinations/data/hyperdx.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
apiVersion: internal.odigos.io/v1beta1
kind: Destination
metadata:
type: hyperdx
displayName: HyperDX
category: managed
spec:
image: hyperdx.svg
signals:
traces:
supported: true
metrics:
supported: true
logs:
supported: true
fields:
- name: HYPERDX_ENDPOINT
displayName: OTLP gRPC Endpoint
componentType: input
initialValue: 'in-otel.hyperdx.io:4317'
componentProps:
type: text
required: true
- name: HYPERDX_API_KEY
displayName: HyperDX API Key
componentType: input
secret: true
componentProps:
type: password
required: true
7 changes: 7 additions & 0 deletions destinations/logos/hyperdx.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions docs/backends-overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ Odigos has destinations for many observability backends.
| Google Cloud Storage | Managed | ✅ | | ✅ |
| Grafana Cloud | Managed | ✅ | ✅ | ✅ |
| Honeycomb | Managed | ✅ | ✅ | ✅ |
| HyperDX | Managed | ✅ | ✅ | ✅ |
| Jaeger | Self-Hosted | ✅ | | |
| Last9 | Managed | ✅ | ✅ | |
| Lightstep | Managed | ✅ | | |
Expand Down
58 changes: 58 additions & 0 deletions docs/backends/hyperdx.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: 'HyperDX'
---

## Configuring Backend

- **HYPERDX_ENDPOINT** - OpenTelemetry gRPC Endpoint, defaults to `in-otel.hyperdx.io:4317`.
- **HYPERDX_API_KEY** - HyperDX API Key.

## Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

1. **Using the UI**

Use the [Odigos CLI](https://docs.odigos.io/cli/odigos_ui) to access the UI:

```bash
odigos ui
```

2. **Using kubernetes manifests**

Save the YAML below to a file (e.g., `destination.yaml`) and apply it using `kubectl`:

```bash
kubectl apply -f destination.yaml
```


```yaml
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
name: hyperdx-example
namespace: odigos-system
spec:
data:
HYPERDX_ENDPOINT: <OTLP gRPC Endpoint>
destinationName: hyperdx
secretRef:
name: hyperdx-secret
signals:
- TRACES
- METRICS
- LOGS
type: hyperdx

---
apiVersion: v1
data:
HYPERDX_API_KEY: <base64 HyperDX API Key>
kind: Secret
metadata:
name: hyperdx-secret
namespace: odigos-system
type: Opaque
```
Loading
Loading