-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: Sematext Exporter #36465
Comments
@andrzej-stencel does this look good now and can this issue be assigned to me |
@andrzej-stencel please review? |
This component was originally proposed before the rules for vendor components were changed. I think it's fair to still accept it, therefore I declare to sponsor this component. |
#### Description First PR of New component: Sematext Exporter. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue #36465 --------- Co-authored-by: Andrzej Stencel <[email protected]>
…37161) #### Description First PR of New component: Sematext Exporter. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#36465 --------- Co-authored-by: Andrzej Stencel <[email protected]>
…7642) Description: Second PR of New component: Sematext Exporter. Basic Implementation of Metrics. Link to tracking Issue: #36465 --------- Co-authored-by: Andrzej Stencel <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>
) Description: Third PR of New component: Sematext Exporter. Advanced Implementation of Metrics. Link to tracking Issue: #36465
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 |
The purpose and use-cases of the new component
The Sematext Metric Exporter component is designed to export telemetry data, specifically metrics and logs, to the Sematext platform, enabling real-time monitoring, alerting, and observability. This exporter supports sending metrics to Sematext Cloud in Influx line protocol format and logs using the Bulk Index Api format.
The primary changes include:
app_token
for authentication with the Sematext platform.Example configuration for the component
Configuration Options
timeout
(default = 5s) Timeout for requestsRegion
Specifies the Sematext region the user is operating in; must be one of:US
EU
app_token
Specifies the token of the Sematext Monitoring App to which the user wants to send data.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 hereenabled
(default = true) Enables the sending queue.num_consumers
(default = 10) The number of consumers from the queue.queue_size
(default = 1000) Maximum number of batches allowed in the queue at a given time.retry_on_failure
Details hereenabled
(default = true) Enables retries on failure.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:
Telemetry data types supported
Metrics, Logs
Is this a vendor-specific component?
Code Owner(s)
@AkhigbeEromo
Sponsor (optional)
@andrzej-stencel
Additional context
No response
The text was updated successfully, but these errors were encountered: