Rename otelcol components to match upstream semantics

[ptodev]

Component(s)

otelcol.*

Background

There is an ongoing effort to rename some of the upstream otel components to comply with upstream's naming convention. I suspect all those components will eventually be renamed. We could introduce aliases for all renamed components to avoid breaking changes.

The benefits of renaming in Alloy are:

• Easier for users to find what they are looking for. Users will expect Alloy to have a similar name to upstream.
• Currently, some otelcol components have underscores while others do not. The new convention will make all names consistent.
• Non-otelcol Alloy components already tend to use underscores. E.g. prometheus.remote_write, prometheus.receive_http, and local.file_match.

Proposal

The following components will need to be renamed:

• otelcol.connector.servicegraph > otelcol.connector.service_graph
• otelcol.connector.spanlogs > otelcol.connector.span_logs
• otelcol.connector.spanmetrics > otelcol.connector.span_metrics
• otelcol.exporter.awss3 > otelcol.exporter.aws_s3
• otelcol.exporter.googlecloud > otelcol.exporter.google_cloud
• otelcol.exporter.googlecloudpubsub > otelcol.exporter.google_cloud_pub_sub
• otelcol.exporter.loadbalancing > otelcol.exporter.load_balancing
• otelcol.exporter.otlphttp > otelcol.exporter.otlp_http
• otelcol.exporter.splunkhec > otelcol.exporter.splunk_hec
• otelcol.processor.cumulativetodelta > otelcol.processor.cumulative_to_delta
• otelcol.processor.deltatocumulative > otelcol.processor.delta_to_cumulative
• otelcol.processor.groupbyattrs > otelcol.processor.group_by_attrs
• otelcol.processor.k8sattributes > otelcol.processor.k8s_attributes
• otelcol.processor.resourcedetection > otelcol.processor.resource_detection
• otelcol.receiver.awscloudwatch > otelcol.receiver.aws_cloudwatch
• otelcol.receiver.awsecscontainermetrics > otelcol.receiver.aws_ecs_container_metrics
• otelcol.receiver.filelog > otelcol.receiver.file_log
• otelcol.receiver.fluentforward > otelcol.receiver.fluent_forward
• otelcol.receiver.googlecloudpubsub > otelcol.receiver.google_cloud_pub_sub
• otelcol.receiver.splunkhec > otelcol.receiver.splunk_hec

Tip

_{React with 👍 if this issue is important to you.}