[exporter/awsemf] set default dimension_rollup_option to NoDimensionRollup

[abarganier]

Component(s)

exporter/awsemf

Is your feature request related to a problem? Please describe.

Currently, the dimension_rollup_option defaults to ZeroAndSingleDimensionRollup. This leads to an expensive explosion of metric counts in CloudWatch once ingested.

For example, if you have a metric:
my_metric{label1="a", label2="b"}

The CloudWatch exporter was exporting this as three unique metrics (potentially more?):

my_metric{label1="a", label2="b"}
my_metric{label1="a"}
my_metric{label2="b"}

As with most standard timeseries databases/monitoring systems, the default behavior here should be to just treat this is a single metric, my_metric{label1="a", label2="b"}.

To have the default behavior be anything different leads to large CloudWatch bills, where billing is done per-metric. This means that exploding a single metric into multiple drives the bill up considerably, and quite frankly, since I don't see any utility in decomposing a label set into multiple metrics per-label, it seems like the bill is high for no good reason.

Describe the solution you'd like

The default value of dimension_rollup_option should be NoDimensionRollup to avoid unexpected huge CloudWatch bills, where users can "opt-in" to the more expensive options if they choose to.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/awsemf: @Aneurysm9 @shaochengwang @mxiamxia

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[bryan-aguilar]

Hi @abarganier, thanks for bringing up this issue. I think the cost of the zeroandsingle dimension is a concern for many. While I can't comment on the reasoning for the default being set to ZeroAndSingleDimension rollup I do agree that NoDimensionRollup would be better suited as a default option. I will work on a PR for this and will link to this issue when ready.

[abarganier]

@bryan-aguilar thank you for the response. Would love to see this merged & eventually become the default.

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

Pinging code owners:

• exporter/awsemf: @Aneurysm9 @shaochengwang @mxiamxia @bryan-aguilar

See Adding Labels via Comments if you do not have permissions to add labels yourself.

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