[PR] Enhancement of SignalToMetricsConnector: Key Name Override & Null Value Handling

[capiisco]

Context
Currently with SignalToMetricsConnector, when configuring a logs based metric using attribute/resource keys as tags, renaming a key requires creating a new attribute with the desired name. This approach leads to data duplication and a more complex configuration.

Additionally, if a default value is not set for a non-existent attribute key, the metric is not counted, which can result in data loss.

Proposed Changes
Add a name field to allow overriding the name of a key without creating a new attribute.

Example configuration after the change:
yaml

Modifier

• name: poc1.kong.http.count
  description: Count of log records
  conditions:
  • Int(attributes["http.status_code"]) > 0
    include_resource_attributes:
  • key: service
    attributes:
  • key: bu_code
    default_value: "N/A"
    name: "custom_bu_code"
  • key: consumer_id
    default_value: "N/A"
    name: "custom_consumer_id"

Here, the bu_code key will be used as custom_bu_code without duplicating data.

Handle null values properly:
Currently, if an attribute key is missing and no default value is defined, the metric is not counted.
This fix ensures that the component handles missing attributes without requiring an explicit default value.

Impact & Benefits

• Reduces attribute duplication.
• Simplifies configuration.
• Prevents metric loss when attribute keys are missing.