AWS: TargetResponseTime metrics added to Application elb

[anil-elastic]

Proposed commit message

Added TargetResponseTime metrics in AWS Application ELB.

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.

Author's Checklist

• [ ]

How to test this PR locally

I've tested with elastic-package, and run the tests and TargetResponseTime comes into elb metrics.

"aws": {
      "applicationelb": {
        "metrics": {
          "HealthyHostCount": {
            "max": 1
          },
          "RequestCount": {
            "sum": 4
          },
          "TargetResponseTime": {
            "avg": 0.0014383333333333333
          },
          "UnHealthyHostCount": {
            "max": 0
          }
        }
      },

• Closes Add TargetResponseTime metric in ELB agent configuration, #9201

Screenshots

[cla-checker-service]

💚 CLA has been signed

[anil-elastic]

/test

[gpop63]

/test

[agithomas]

I understand this is a simple enhancement.

Is there a plan to display the newly added field under the existing dashboard?

This change must be considered alongside other issues mentioned here, especially the challenges of dashboarding for ELB metrics and logs.

[agithomas]

Reviews shared.

[agithomas]

Please regenerate the README, checkin the README changes to avoid buildkite failure.

[agithomas]

Comments added

[anil-elastic]

/test

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[ishleenk17]

@lucabelluccini : I think this was the customer enhancement request you were discussing with me.
The PR is already in works for adding the TargetResponseTime metric.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a956561

History

• 💚 Build #12713 succeeded c2b11fc
• 💔 Build #12708 failed c2b11fc
• 💔 Build #12683 failed 5e75e8f
• 💔 Build #12634 failed 0143a88

cc @anil-elastic

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[anil-elastic]

Reply to @agi comment: #10181 (comment)

I had discussion with @agi and according to @agithomas Customers are often getting confused with empty fields in their dashboard.There is ongoing issue to split elb data stream into 3 different data streams: application_elb, network_elb, and classic_elb as mentioned in this ticket #4800.

I have also created backlog ticket for create a dashboard panel for ALB.
#10326

[agithomas]

I understand this is a simple enhancement.

Is there a plan to display the newly added field under the existing dashboard?

This change must be considered alongside other issues mentioned here, especially the challenges of dashboarding for ELB metrics and logs.

Based on my discussion with @anil-elastic , i understand the field is relevant when an ALB is configured.

Adding a dashboard panel at this stage will add more problems to the customers as mentioned here.

Hence the #10326 is created as a backlog issue, which can be taken up along with the enhancement request of separate OOTB dashboards for various LBs

[agithomas]

LGTM!

[elasticmachine]

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