Add support for configuring EFA receiver on EC2 via JSON

[mitali-salvi]

Description of the issue

Add support for configuring the awsefareceiver via the CWA JSON configuration. Customers will be able to configure EFA (Elastic Fabric Adapter) metrics collection under metrics.metrics_collected.efa.

EFA is a distinct hardware type (Elastic Fabric Adapter) that exposes 22 cumulative monotonic sum metrics via /sys/class/infiniband/ sysfs. The receiver is a native OTel receiver (not adapter-based) that runs in the hostDeltaMetrics pipeline with cumulative-to-delta processing.

Configuration Examples

{
  "metrics": {
    "metrics_collected": {
      "efa": {
        "measurement": ["efa_tx_bytes", "efa_rx_bytes", "efa_rdma_read_bytes"],
        "metrics_collection_interval": 30
      }
    }
  }
}

{
  "metrics": {
    "metrics_collected": {
      "efa": {
        "measurement": ["tx_bytes", "rx_dropped"]
      }
    }
  }
}

{
  "metrics": {
    "aggregation_dimensions": [["aws.efa.device"]],
    "metrics_collected": {
      "efa": {
        "measurement": ["efa_tx_bytes", "efa_rx_bytes"],
        "drop_original_metrics": ["efa_tx_bytes", "efa_rx_bytes"]
      }
    }
  }
}

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests

• Unit tests: 9 test cases all passing (including wildcard and measurement-required error cases)
• Manual: deployed CWA to EC2 instance with EFA devices, generated traffic between two EFA-enabled instances, confirmed agent starts and collects metrics

Requirements

Before committing your code, please do the following steps.

1. Run make fmt and make fmt-sh
2. Run make lint

Integration Tests

To run integration tests against this PR, add the ready for testing label.

[github-actions]

This PR was marked stale due to lack of activity.

[sky333999]

Need to add goldel yaml tests

[mitali-salvi]

The existing tests already use the golden JSON→YAML pattern (testdata/.json input → testdata/.yaml expected output). We now have 9 test cases covering: selective metrics, non-prefixed names, empty measurements, wildcard, measurement-required errors, and interval overrides. Added wildcardConfig.json/yaml golden pair. See commit 4e79df7.

[sky333999]

By the golden yaml tests, I mean the ones in translator/tocwconfig/sampleConfig/ that test the end to end pipelines and not just the individual components. You could probably add this to the complete linux one.

[sky333999]

Mind posting a screenshot of what the actual metrics look like in the CW metrics console? Do they have device and interfaceID as dimensions? Without host/InstanceId, are these currently getting aggregated to the account level?