Document input metrics

[andrewkroh]

Update the documentation for Filebeat, Winlogbeat, and Packetbeat to include a description of the metrics associated with the following inputs.

Inputs

• [ ] filebeat/aws-cloudwatch https://github.com/elastic/beats/blob/f74ba6910618d49a84f130f2b1bfb136ba647bfd/x-pack/filebeat/input/awscloudwatch/metrics.go#L15-L18
• [ ] filebeat/cel https://github.com/elastic/beats/blob/e00506e58343327c9ee3c8b482abf589557c02a1/x-pack/filebeat/input/cel/input.go#L927-L934
• [ ] winlogbeat/winlog https://github.com/elastic/beats/blob/71530c4682f4a0015110f4656d17ab71857b31ff/winlogbeat/eventlog/wineventlog.go#L652-L658
• [ ] packetbeat/tcp https://github.com/elastic/beats/blob/37ddd1e4daa5c5679cf49a846b3f80d315966a24/packetbeat/protos/tcp/tcp.go#L395-L401
• [ ] packetbeat/udp https://github.com/elastic/beats/blob/7356c98624eeac01b545804d0e10acfde8e180c7/packetbeat/protos/udp/udp.go#L145-L149

Existing Examples

• filebeat/tcp
• filebeat/udp
• filebeat/unix
• filebeat/aws-s3

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[andrewkroh]

For consistency and to steer users toward the documented /inputs/ endpoint, we should update the existing metrics docs in 8.7 and beyond with

from:

These metrics are exposed under the /dataset path.

to:

These metrics are exposed under the /inputs path.