Update CHANGELOG.md and config docs

CHANGELOG.md

@@ -1,5 +1,6 @@
 ## main / unreleased
 * [FEATURE] tempo-cli: support dropping multiple traces in a single operation [#4266](https://github.com/grafana/tempo/pull/4266) (@ndk)
+* [CHANGE] update default config values to better align with production workloads [#4340](https://github.com/grafana/tempo/pull/4340) (@electron0zero)
 * [CHANGE] **BREAKING CHANGE** The Tempo serverless is now deprecated and will be removed in an upcoming release [#4017](https://github.com/grafana/tempo/pull/4017/) @electron0zero
 * [CHANGE] **BREAKING CHANGE** Change the AWS Lambda serverless build tooling output from "main" to "bootstrap". Refer to https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-from-the-go1-x-runtime-to-the-custom-runtime-on-amazon-linux-2/ for migration steps [#3852](https://github.com/grafana/tempo/pull/3852) (@zatlodan)
 * [CHANGE] Add throughput and SLO metrics in the tags and tag values endpoints [#4148](https://github.com/grafana/tempo/pull/4148) (@electron0zero)

docs/sources/tempo/configuration/_index.md

@@ -532,7 +532,7 @@ metrics_generator:
     # This option only allows spans with end times that occur within the configured duration to be
     # considered in metrics generation.
     # This is to filter out spans that are outdated.
-    [metrics_ingestion_time_range_slack: <duration> | default = 30s]
+    [metrics_ingestion_time_range_slack: <duration> | default = 2m0s]
 
     # Timeout for metric requests
     [query_timeout: <duration> | default = 30s ]
@@ -639,7 +639,7 @@ query_frontend:
         [throughput_bytes_slo: <float> | default = 0 ]
 
         # The number of shards to break ingester queries into.
-        [ingester_shards]: <int> | default = 1]
+        [ingester_shards]: <int> | default = 3]
 
         # SLO configuration for Metadata (tags and tag values) endpoints.
         metadata_slo:
@@ -1571,7 +1571,7 @@ overrides:
       # tags with high cardinality or large values such as HTTP URLs or SQL queries.
       # This override limit is used by the ingester and the querier.
       # A value of 0 disables the limit.
-      [max_bytes_per_tag_values_query: <int> | default = 5000000 (5MB) ]
+      [max_bytes_per_tag_values_query: <int> | default = 1000000 (1MB) ]
 
       # Maximum number of blocks to be inspected for a tag values query. Tag-values
       # query is used mainly to populate the autocomplete dropdown. This limit