Adjust validation if Metric and MetricNamespace monikers to ingestion requirements

The naming restrictions for metrics are stricter at the new endpoint compared to the AppInsights unauthenticated endpoint. The existing (stable) APIs should not be changed (back-compat). However new pre-aggregation APIs should fail-fast when invalid monikers are used. We have already included some of this validation into the first Beta, but we need to re-align them with the public endpoint shipped version:

• Metric Namespace moniker may be exceed 256 characters.
• Metric Name moniker may be exceed 256 characters.
• Metric Namespace may not start with “Microsoft.”.
• Metric Namespace may not be equal to any of the following: – GenevaKustoQos – LogsToMetricsQos – MdmQos – RecoveryService/V2 – MonitorSLA – WarmPathQos

[macrogreg]

Ok. I’ll take a look. If I do not find anything, I will create a generic internal utility that can be used by other places too, but I may not have capacity to go through similar usages elsewhere and rewire them to use the generic solution.

It’ll be something similar to:

string EnsureValidMoniker(string moniker, int maxLen, char[] invalidChars, char asciiEscape);

Works?

[github-actions[bot]]

This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 7 days.