Consider renaming awscontainerinsightreceiver to awscontainerinsight

[dmitryax]

The component name (not package name) shouldn't include receiver suffix.

Users have to configure it like

receivers:
  awscontainerinsightreceiver:

instead of

receivers:
  awscontainerinsight:

or

receivers:
  aws_container_insight:

as any other receiver.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners for receiver/awscontainerinsight: @Aneurysm9 @pxaws. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triage' to set the priority and remove the needs-triage label.

[woody1872]

All the receivers have the "receiver" suffix. Why should this receiver be different?

I don't like the suffix myself, but I do appreciate consistency and naming standards.

[dmitryax]

All the receivers have the "receiver" suffix

You likely confuse it with package name, not the receiver type that is being used in the user config

[JaredTan95]

It seems there's a breaking change

[VihasMakwana]

@dmitryax I'm in support of this change. As per our stability doc for alpha components, we should give a notice about the renaming (preferably on CNCF slack), as this will be a breaking change.

After one or two releases, we can rename the component and we should be good to go.

[ishaish103]

@dmitryax can i be assigned?