New component: Sematext Exporter

[ghost]

The purpose and use-cases of the new component

The Sematext Metric Exporter component is designed to export telemetry data, specifically metrics, to the Sematext platform, enabling real-time monitoring, alerting, and observability. This exporter is an extension of the existing InfluxDB exporter, leveraging Sematext's capability to listen over the Influx line protocol.

The primary changes include:

• The addition of an app_token for authentication with the Sematext platform.
• Introduced Region to specify the data storage location

Example configuration for the component

Configuration Options:

• timeout (default = 5s) Timeout for requests
• Region Region specifies the Sematext region the user is operating in; must be one of:
  • US
  • EU
• app_token App token specifies the token of Sematext Monitoring App to which the user wants to send data to.
• payload_max_lines (default = 1_000) Maximum number of lines allowed per HTTP POST request
• payload_max_bytes (default = 300_000) Maximum number of bytes allowed per HTTP POST request
• metrics_schema (default = telegraf-prometheus-v2) The chosen metrics schema to write
• sending_queue details here
  • enabled (default = true)
  • num_consumers (default = 10) The number of consumers from the queue
  • queue_size (default = 1000) Maximum number of batches allowed in queue at a given time
• retry_on_failure details here
  • enabled (default = true)
  • initial_interval (default = 5s) Time to wait after the first failure before retrying
  • max_interval (default = 30s) Upper bound on backoff interval
  • max_elapsed_time (default = 120s) Maximum amount of time (including retries) spent trying to send a request/batch

The full list of settings exposed for this exporter are documented in config.go.

Example:

timeout: 500ms
region: US  
retry_on_failure:
  enabled: true
  initial_interval: 1s
  max_interval: 3s
  max_elapsed_time: 10s
metrics:
  app_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  sending_queue:
    enabled: true
    num_consumers: 3
    queue_size: 10
  payload_max_lines: 100
  payload_max_bytes: 1000

Telemetry data types supported

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)

@Eromosele-SM

Sponsor (optional)
No response

[jackgopack4]

happy to review the PR once you create it, welcome

[atoulme]

Please present your new component proposal at a SIG meeting. You will need a sponsor for this component.

[ghost]

Hello @atoulme
I presented the component in the last SIG meeting
I was told that a sponsor will be randomly selected as this is Sematext first component

[AkhigbeEromo]

I was the one that created this issue
But I used my company GH account to create this issue
At KubeCon I spoke to @andrzej-stencel and he advised I use my normal GH account because I am an official contributor there

So I had to delete my former account and I forgot to close the PRs and issues associated with it
Is it possible to help with that?