Allow remote write tuning for the prometheusremotewriteexporter

[rakyll]

Prometheus server provides a variety of options for the users to fine tune the remote write API calls. These parameters are summarized at https://prometheus.io/docs/practices/remote_write/. prometheusremotewriteexporter should allow users to tweak the exporter in a similar fashion where possible.

cc @jeromeinsf @alolita

[rakyll]

This seems to be a documentation improvement and the exporter config should be already covering a bunch. See the following for the available config options:

min_shards , max_shards -> no true equivalent but QueueSettings.NumConsumers
max_samples_per_send -> QueueSettings.QueueSize
batch_send_deadline -> TimeoutSettings.Timeout
min_backoff -> RetrySettings.InitialInterval
max_backoff -> RetrySettings.MaxInterval

[rakyll]

This is blocked by open-telemetry/opentelemetry-collector#2266.

[rakyll]

With open-telemetry/opentelemetry-collector#2951 merged, we need to prioritize this because we removed the queue from the Prometheus remote write.

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

[bixu]

We may be hitting this behavior in my org:

ts=2024-11-14T16:26:15.172Z caller=write_handler.go:134 level=error component=web msg="Out of order sample from remote write" err="out of order sample" series="{__name__=\"http_server_response_size_bytes_count\", app_name=\"my_app\"}" timestamp=1731601574754