Troubleshoot the Edge Delta Cloud Pipeline

Troubleshooting Edge Delta Cloud Pipelines for HTTP input, OTLP configuration, and connectivity issues.

  5 minute read  

Overview

You can diagnose and resolve common issues with Edge Delta Cloud Pipelines deployed in Edge Delta’s managed infrastructure.

Note: Cloud Pipelines are hosted and managed by Edge Delta. You configure them through the Edge Delta UI and they expose endpoints for data ingestion. Ensure you have the correct pipeline ID and endpoints from the Pipeline Settings page.

1. Check Pipeline Status

Verify that your Cloud Pipeline is running correctly.

Navigate to Pipelines in the Edge Delta UI and check your Cloud Pipeline’s status:

  • Active: Pipeline is running and accepting data
  • Suspended: Pipeline is paused and not consuming resources
  • Error: Pipeline has configuration or runtime issues

Check the following indicators:

  • Last activity timestamp to confirm recent data processing
  • Compute unit utilization percentage
  • Any error notifications or warnings in the UI

2. Verify Endpoint Configuration

Inspect the Cloud Pipeline endpoints in the Settings tab.

Check for the correct endpoint formats:

  • HTTP Endpoint: https://{pipeline-id}-http-{region}-cf.aws.edgedelta.com
  • GRPCS Endpoint: {pipeline-id}-grpc-{region}-cf.aws.edgedelta.com:443

Common endpoint format issues:

  • gRPC: Do not include grpcs:// prefix - use only the hostname and port
  • HTTP: Must include https:// prefix for secure connections
  • Port numbers: Use port 443 for HTTPS/TLS connections, port 80 for non-TLS HTTP connections

3. Test HTTP Input Connectivity

Validate that HTTP input nodes are receiving data.

Test a basic HTTP input:

curl -X POST -d '{"test":"message"}' \
  https://your-pipeline-id-http-us-west2-cf.aws.edgedelta.com/test

Check for these response codes:

  • 200 OK: Data received successfully
  • 401 Unauthorized: Authentication required or invalid credentials
  • 404 Not Found: Path doesn’t match any included_paths filter
  • 503 Service Unavailable: Pipeline suspended or overloaded

For authenticated endpoints, use Bearer token authentication or Basic authentication:

curl -X POST -H "Authorization: Bearer your_token" \
  -d '{"test":"message"}' \
  https://your-pipeline-endpoint.edgedelta.com/path

curl -X POST -u username:password \
  -d '{"test":"message"}' \
  https://your-pipeline-endpoint.edgedelta.com/path

4. Diagnose Multiple HTTP Input Issues

Troubleshoot data duplication when using multiple HTTP inputs.

Review your HTTP input configuration for path filtering. Each HTTP input must have unique path patterns that don’t overlap. When using multiple HTTP inputs, they must all use the same port (either 80 for HTTP or 443 for HTTPS):

nodes:
- name: http_input_1
  type: http_input
  port: 80
  included_paths:
    - /service-a/.*

- name: http_input_2
  type: http_input
  port: 80
  included_paths:
    - /service-b/.*

Common issues and fixes:

  • Data duplication: Missing or overlapping included_paths patterns - ensure each HTTP input has unique path filters
  • Port conflicts: All HTTP inputs must use the same port (80 for HTTP or 443 for HTTPS/TLS)
  • Rejected requests: Path doesn’t match any configured included_paths pattern
  • No path filtering: Single HTTP input without included_paths accepts all paths

5. Validate OTLP Exporter Configuration

Check OpenTelemetry Collector connection to Cloud Pipeline.

For gRPC exporters, do not include the grpcs:// prefix in the endpoint:

exporters:
  otlp/edgedelta:
    endpoint: 'pipeline-id-grpc-us-west2-cf.aws.edgedelta.com:443'
    tls:
      insecure: false

For HTTP exporters, you must include the https:// prefix and disable compression:

exporters:
  otlphttp/edgedelta:
    endpoint: 'https://pipeline-id-http-us-west2-cf.aws.edgedelta.com:443'
    compression: none
    tls:
      insecure: false

Test OTLP connectivity using these commands:

grpcurl -d '{}' pipeline-id-grpc-us-west2-cf.aws.edgedelta.com:443 list

curl -X POST https://pipeline-id-http-us-west2-cf.aws.edgedelta.com:443/v1/logs

The first command tests the gRPC endpoint, and the second tests the HTTP endpoint.

6. Review Pipeline Logs

Check the live logs for your Cloud Pipeline in the Edge Delta UI.

Navigate to your pipeline and click Live Logs to see:

  • Incoming data samples
  • Processing errors or warnings
  • Destination connection failures
  • Configuration validation errors

Filter logs by:

  • Severity level (ERROR, WARN, INFO, DEBUG)
  • Time range
  • Specific node names
  • Error patterns

7. Monitor Compute Unit Usage

Check if the pipeline is hitting resource limits.

In Pipeline Settings, review:

  • Current Usage: Percentage of allocated compute units being used
  • Peak Usage: Maximum usage in the last 24 hours
  • Data Rate: Current MB/s ingestion rate

Signs of resource constraints:

  • Usage consistently above 80%
  • Data lag or backpressure warnings
  • Dropped connections or timeout errors
  • Slow response times

To increase capacity:

  1. Navigate to Pipeline Settings
  2. Adjust Compute Units (each unit handles ~12 MB/s or 1 TB/day)
  3. Save changes (takes effect within minutes)

8. Troubleshoot Destination Connectivity

Diagnose issues with data not reaching configured destinations.

Check destination node configuration:

  • API keys and credentials are valid
  • Endpoint URLs are correct and accessible
  • Data format matches destination requirements

Common destination issues:

  • Authentication failures: Invalid or expired API keys
  • Rate limiting: Destination rejecting data due to rate limits
  • Format mismatches: Data structure incompatible with destination
  • Network timeouts: Firewall or connectivity issues

Test destination connectivity from the UI:

  1. Navigate to your pipeline configuration
  2. Click on the destination node
  3. Use the Test button to validate connectivity

9. Validate Path Filtering Rules

Ensure included_paths regex patterns work as expected.

Test your regex patterns in the included_paths configuration. The first pattern matches any path starting with /api/v1/, the second matches paths starting with /logs/, and the third matches exactly /metrics:

included_paths:
  - /api/v1/.*
  - /logs/.*
  - /metrics$

Common regex issues:

  • Missing .* for wildcard matching
  • Incorrect escape sequences
  • Overlapping patterns between nodes
  • Case sensitivity (patterns are case-sensitive by default)

10. Check Agent Version Compatibility

Ensure your Cloud Pipeline uses a compatible agent version.

In Pipeline Settings:

  • Review current agent version
  • Check for available updates
  • Select stable versions (avoid rc/candidate versions unless advised)

Update procedure:

  1. Navigate to Pipeline Settings
  2. Select new agent version from dropdown
  3. Save changes
  4. Monitor pipeline logs for any compatibility issues

11. Reset Pipeline Configuration

If configuration issues persist, reset to a known working state.

Steps to reset:

  1. Export current configuration for backup
  2. Create a new Cloud Pipeline with default settings
  3. Test basic connectivity
  4. Gradually add your configuration back
  5. Test after each configuration change

12. Contact Support

If issues persist after troubleshooting, contact Edge Delta support with:

  • Pipeline ID
  • Time range when issue occurred
  • Configuration snippet (remove sensitive data)
  • Error messages from logs
  • Steps already attempted

Access support through:

  • Edge Delta UI support chat
  • Support portal ticket
  • Email to support team