cisco_aironet: add ECS mapping for destination.port

[zmoog]

Proposed commit message

Add ECS mapping for the destination.port field (long type).

Users reported mapping exceptions due to destination.port string values causing field mapping as keyword instead of long. See the related issue.

Elasticsearch maps a field as a keyword if it has a string value. This happens even on stack versions 8.13+ because ecs@mappings does not perform type coercion.

By adding the destination.port field to the file fields/ecs.yml, we ensure Elasticsearch uses the expected ECS field mapping as long even when the value is a string.

IMPORTANT: To fully resolve the issue, the input/integration owner should update it to emit the right value type to leverage ecs@mappings.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Related issues

• Relates Verify mapping problems after migrating to ecs@mappings #10848

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: bd7b939

History

• 💚 Build #15799 succeeded b06fc4f

cc @zmoog

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elastic-vault-github-plugin-prod]

Package cisco_aironet - 1.14.1 containing this change is available at https://epr.elastic.co/search?package=cisco_aironet