New component: Demo Logs receiver

[legendary-acp]

The purpose and use-cases of the new component

While debugging data path from collector to desired location we sometime need some random data that generate some random logs generated for debugging purpose. It would be great if we create a dummy log receiver within collector which will solve our use case.

Example configuration for the component

receivers:
  dummyLogs:
    body: "This is a demo log"

This is very vague overview. Can be changed in future depending on usecase.

Telemetry data types supported

Primarily for logs but later can be extended to traces and metrics.

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

No response

[legendary-acp]

I would love to sponsor this if this sounds interesting

[atoulme]

Thank you for submitting this proposal!

We already have telemetrygen and the otlpjsonfilereceiver to produce data according to a rate and signal, or a fixed static file. Would you please investigate if those provide enough coverage for your use case?

Only an approver or maintainer may be a sponsor of new components. Please review https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components for more information.

[legendary-acp]

telemetrygen is exactly my use case. But I was wondering instead of making it a separate command can't we convert it into receiver component? Something like fluentbit dummy input does.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.