New component: Logicmonitor exporter

[khyatigandhi6]

The purpose and use-cases of the new component

Logicmonitor exporter will send trace and log data to Logicmonitor platform (https://www.logicmonitor.com/).

Example configuration for the component

Configuration Options

The following configuration options are supported:

url (required): The address to send logs and traces
apitoken : API Token of Logicmonitor
headers: Headers of POST requests
log_batching_enabled(default = true) : The flag to enable/disable logs batching
log_batching_interval(default = 10s) : The time interval for log batching

Example Configuration

Ingestion through API Token

  exporters:
    logicmonitor:
      url: "https://<company_name>.logicmonitor.com/rest"
      apitoken:
        access_id: "<access_id of logicmonitor>"
        access_key: "<access_key of logicmonitor>"

OR

Ingestion through Bearer token

  exporters:
    logicmonitor:
      url: "https://<company_name>.logicmonitor.com/rest"
      headers:
        Authorization: Bearer <bearer token of logicmonitor>

Telemetry data types supported

Traces and logs

Is this a vendor-specific component? If so, are you proposing to contribute this as a representative of the vendor?

Yes it is a vendor-specific component.

Sponsor (Optional)

No sponsor as of now. Help me find a sponsor.

[evan-bradley]

Just to confirm, are you proposing to contribute this as a representative of the vendor?

[khyatigandhi6]

Yes @evan-bradley . PR is ready. I will raise it once I get go-ahead.

[evan-bradley]

Thanks. One of the available sponsors may volunteer to sponsor the component on this issue. Otherwise, you can request for someone to sponsor at the Collector SIG meeting which is held on Wednesdays at 16:00 UTC, or a sponsor will be selected from the rotation.

[khyatigandhi6]

As per the discussion in the last SIG meeting, sponsor will be selected from the rotation.

[khyatigandhi6]

I have raised the PR (#14182) against this issue.
Can someone please have a look at it ?

[dmitryax]

I got another component and moved myself to the bottom of the queue. I believe this one should be taken @bogdandrutu now as the next in the list

[lalit-fgr]

@dmitryax - any process to be followed by vendor for this?

[jpkrohling]

@bogdandrutu, it looks like you are the assigned sponsor for this one.

[lalit-fgr]

@khyatigandhi6 can you please resolve the merge conflicts
@bogdandrutu any guidance will be highly appreciated

[khyatigandhi6]

@bogdandrutu , the ticket still has label 'Sponsor Needed'. Can you please assign the ticket to yourself or to the one who is next in the sponsor list so that the PR review process gets started.
Any guidance and help will be appreciated as I am new to this :)

[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.

[khyatigandhi6]

Hi @bogdandrutu,
I have updated the PR #16608 with the suggested changes. Could you please have a look at it once more?

[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.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.