APM UI changes for serverless services / AWS lambda

[gbamparop]

Closes #106552

Requires elastic/apm-server#6576 to properly work with metric documents.

Summary

Some APM agents now support AWS lambda instrumentations. In this context some of the data is not available while some additional, serverless-specific information is available that is very valuable for APM use cases. This PR contains UI changes to reflect these aspects for serverless services.

With AWS lambda currently all kind of metric collection are disabled at the agents. Thus, metrics for system, JVM, transaction breakdown are not available.

Screen.Recording.2022-01-28.at.12.18.52.mov

Changes

• Added meta-information for AWS lambda services in the service-icons panel
  

• Added cloud.service.name and cloud.region (before only availability zone was shown) as additional info being shown in cloud metainfo section
  

• Replaced transaction breakdown chart with cold start rate chart for serverless services

  • In service overview
    

  • In transactions overview
    

  • In transaction details
    

• Added cold start badge to waterfall transaction items (when they represent cold start requests)
  

• Added cold start badge to transaction flyout (when it represents cold start requests)
  

• Hidden metrics-related views (for which metrics are not available)

  • Instances latency distribution chart and instance table
  • Metrics and JVM tab

Testing

Synthtrace

Run the following scenario with synthrace CLI

aws_lambda_with_multiple_functions.ts.zip

Cloud

@gbamparop can help to set this up.

1. Create a deployment using the latest snapshot (e.g. 8.1.0-SNAPSHOT)
2. Add lambda extension and instrument a lambda function by following this guide
3. Invoke the lambda function to ingest data in APM
4. Connect local kibana instance to the cloud

Todo

• Docs: Additions for charts and transaction view changes etc ([Request] AWS Lambda support in the APM UI observability-docs#1490) (pending screenshots with real data)

[gbamparop]

@elasticmachine merge upstream

[gbamparop]

@formgeist shall we add the coldstart badge to the transaction flyout as well? Also, if there's a requirement to have a beta badge for this piece of work where do you think it's the best place to add it?

[formgeist]

@formgeist shall we add the coldstart badge to the transaction flyout as well?

Yes, I think it makes sense similar to the async badge in this example;

Also, if there's a requirement to have a beta badge for this piece of work where do you think it's the best place to add it?

I think the only place where I think it has the most impact is when the user clicks on the Lambda service icon and looks at the content. So adding a EuiBetaBadge (EUI docs) which will show a tooltip on hover.

cc @alex-fedotyev

[gbamparop]

@formgeist thanks, I'll get those added

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[gbamparop]

@elasticmachine merge upstream

[alex-fedotyev]

@gbamparop - do you know why docker icon is displayed next to lambda icon on some of the screenshots?
Is that discrepancy in your test data, or something we need to have logic for to better prioritize?

cc @AlexanderWert

[AlexanderWert]

do you know why docker icon is displayed next to lambda icon on some of the screenshots?
Is that discrepancy in your test data, or something we need to have logic for to better prioritize?

I'd guess it's because the data comes from Synthtrace which in addition to the Lambda fields also generated some docker fields. Shouldn't happen with real data.

@gbamparop correct me if I'm wrong.

[formgeist]

On a related note, has anyone opened an issue for adding a Lambda service to our fleet of Opbeans test data for continued testing?

[gbamparop]

do you know why docker icon is displayed next to lambda icon on some of the screenshots?
Is that discrepancy in your test data, or something we need to have logic for to better prioritize?

I'd guess it's because the data comes from Synthtrace which in addition to the Lambda fields also generated some docker fields. Shouldn't happen with real data.

@gbamparop correct me if I'm wrong.

This is it, I've put as much data as I could in synthrace to help write some tests.

[gbamparop]

@gbamparop Do you think it's possible that when we list out badges that just keep the badges to float as exemplified here;

As discussed we decided to go with the current version for now as there can be several functions with large names and the popup can get quite large.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: a04d9a6
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
apm	1180	1183	+3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
apm	2.8MB	2.8MB	+6.0KB

History

• 💔 Build #20545 failed 22fdd59
• 💚 Build #20351 succeeded 09f8ac3
• 💚 Build #20247 succeeded db451d3
• 💔 Build #20209 failed f6fbaa8
• 💚 Build #20162 succeeded a605812

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @gbamparop

[kibanamachine]

💔 Backport failed

The pull request could not be backported due to the following error:
There are no branches to backport to. Aborting.

How to fix

Re-run the backport manually:

node scripts/backport --pr 122775

Questions ?

Please refer to the Backport tool documentation

[kpatticha]

@gbamparop do you think the scenario aws_lambda_with_multiple_functions.ts.zip would be useful as an example in https://github.com/gbamparop/kibana/tree/aws-lambda/packages/elastic-apm-synthtrace/src/scripts/examples ?

[gbamparop]

@gbamparop do you think the scenario aws_lambda_with_multiple_functions.ts.zip would be useful as an example in https://github.com/gbamparop/kibana/tree/aws-lambda/packages/elastic-apm-synthtrace/src/scripts/examples ?

I think that the intention was to just have a few generic examples as a base point in that folder so didn't add that in. Happy to get it added if this is what we aim for. @dgieselaar what do you think?