Allow custom suffix for trace ingestion index alias

[chenqi0805]

Is your feature request related to a problem? Please describe.
Currently our trace ingestion index alias are reserved to be
spans: otel-v1-apm-span
service-map: otel-v1-service-map
There are user requests to allow custom suffix appended to the above

Describe the solution you'd like
add an index alias suffix setting for trace analytics index.

Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[YANG-DB]

Hi @chenqi0805
I would add to this - add generic support for custom index naming convention as described here for example

[dlvenable]

@chenqi0805 , To be sure, this would be a configuration option and not the default. Correct?

[chenqi0805]

@chenqi0805 , To be sure, this would be a configuration option and not the default. Correct?

Yes. It should not be a breaking change

[YANG-DB]

@dlvenable just for clarifying the requirements :

• customizing index name pattern -
  -- type - indicated the observability high level types "logs", "metrics", "traces"
  -- dataset - The field can contain anything that classify the source of the data - first level of customer naming
  -- namespace - Another user defined namespace. Mainly useful to allow grouping of data such as production grade, geography classification - first level of customer naming

• customizing index sequence suffix pattern -
  In addition since data-stream is not supported yet the sequence naming convention should also be customizable - it may be data with custom format of sequence number

The final name should take the next form:
static_prefix-$type-$namespace-$sequence

Examples:

• otel-v1-apm-span-eu-0001
• ss4o-traces-eu-20240101