Adding upstream version 1.34.4.

Signed-off-by: Daniel Baumann <daniel@debian.org>

plugins/outputs/timestream/sample.conf

@@ -0,0 +1,92 @@
+# Configuration for sending metrics to Amazon Timestream.
+[[outputs.timestream]]
+  ## Amazon Region
+  region = "us-east-1"
+
+  ## Amazon Credentials
+  ## Credentials are loaded in the following order:
+  ## 1) Web identity provider credentials via STS if role_arn and
+  ##    web_identity_token_file are specified
+  ## 2) Assumed credentials via STS if role_arn is specified
+  ## 3) explicit credentials from 'access_key' and 'secret_key'
+  ## 4) shared profile from 'profile'
+  ## 5) environment variables
+  ## 6) shared credentials file
+  ## 7) EC2 Instance Profile
+  #access_key = ""
+  #secret_key = ""
+  #token = ""
+  #role_arn = ""
+  #web_identity_token_file = ""
+  #role_session_name = ""
+  #profile = ""
+  #shared_credential_file = ""
+
+  ## Endpoint to make request against, the correct endpoint is automatically
+  ## determined and this option should only be set if you wish to override the
+  ## default.
+  ##   ex: endpoint_url = "http://localhost:8000"
+  # endpoint_url = ""
+
+  ## Timestream database where the metrics will be inserted.
+  ## The database must exist prior to starting Telegraf.
+  database_name = "yourDatabaseNameHere"
+
+  ## Specifies if the plugin should describe the Timestream database upon
+  ## starting to validate if it has access, necessary permissions, connection,
+  ## etc., as a safety check. If the describe operation fails, the plugin will
+  ## not start and therefore the Telegraf agent will not start.
+  describe_database_on_start = false
+
+  ## Specifies how the data is organized in Timestream.
+  ## Valid values are: single-table, multi-table.
+  ## When mapping_mode is set to single-table, all of the data is stored in a
+  ## single table. When mapping_mode is set to multi-table, the data is
+  ## organized and stored in multiple tables. The default is multi-table.
+  mapping_mode = "multi-table"
+
+  ## Specifies if the plugin should create the table, if it doesn't exist.
+  create_table_if_not_exists = true
+
+  ## Specifies the Timestream table magnetic store retention period in days.
+  ## Check Timestream documentation for more details.
+  ## NOTE: This property is valid when create_table_if_not_exists = true.
+  create_table_magnetic_store_retention_period_in_days = 365
+
+  ## Specifies the Timestream table memory store retention period in hours.
+  ## Check Timestream documentation for more details.
+  ## NOTE: This property is valid when create_table_if_not_exists = true.
+  create_table_memory_store_retention_period_in_hours = 24
+
+  ## Specifies how the data is written into Timestream.
+  ## Valid values are: true, false
+  ## When use_multi_measure_records is set to true, all of the tags and fields
+  ## are stored as a single row in a Timestream table.
+  ## When use_multi_measure_record is set to false, Timestream stores each field
+  ## in a separate table row, thereby storing the tags multiple times (once for
+  ## each field). The recommended setting is true. The default is false.
+  use_multi_measure_records = "false"
+
+  ## Specifies the measure_name to use when sending multi-measure records.
+  ## NOTE: This property is valid when use_multi_measure_records=true and
+  ## mapping_mode=multi-table
+  measure_name_for_multi_measure_records = "telegraf_measure"
+
+  ## Specifies the name of the table to write data into
+  ## NOTE: This property is valid when mapping_mode=single-table.
+  # single_table_name = ""
+
+  ## Specifies the name of dimension when all of the data is being stored in a
+  ## single table and the measurement name is transformed into the dimension
+  ## value (see Mapping data from Influx to Timestream for details)
+  ## NOTE: This property is valid when mapping_mode=single-table.
+  # single_table_dimension_name_for_telegraf_measurement_name = "namespace"
+
+  ## Only valid and optional if create_table_if_not_exists = true
+  ## Specifies the Timestream table tags.
+  ## Check Timestream documentation for more details
+  # create_table_tags = { "foo" = "bar", "environment" = "dev"}
+
+  ## Specify the maximum number of parallel go routines to ingest/write data
+  ## If not specified, defaulted to 1 go routines
+  max_write_go_routines = 25