Skip to content

POC: Create transaction in lambda extension and record error results #315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
simitt opened this issue Sep 23, 2022 · 1 comment · Fixed by #340
Closed

POC: Create transaction in lambda extension and record error results #315

simitt opened this issue Sep 23, 2022 · 1 comment · Fixed by #340
Assignees
Labels
aws-λ-extension AWS Lambda Extension enhancement New feature or request v8.6.0
Milestone

Comments

@simitt
Copy link
Contributor

simitt commented Sep 23, 2022

This enhancement issue to build a POC to investigate creating transaction events on behalf of the Lambda function, and report an error result (e.g. "OutOfMemory") in transaction.result in case an error occurs.

Related go agent work: elastic/apm-agent-go#1323

** Needs more definition **

@simitt simitt added the enhancement New feature or request label Sep 23, 2022
@simitt simitt added this to the 8.6 milestone Sep 23, 2022
@github-actions github-actions bot added the aws-λ-extension AWS Lambda Extension label Sep 23, 2022
@simitt simitt changed the title Create transaction in lambda extension and record error results POC: Create transaction in lambda extension and record error results Sep 23, 2022
@axw
Copy link
Member

axw commented Sep 30, 2022

My expectation is that eventually, the transaction document will capture:

  • the error result, e.g. OutOfMemory or TimedOut
  • Lambda/faas attributes and metrics

The document would look something like

{
  "transaction": {
    "name": "...",
    "result": "OutOfMemory"
  },
  "faas": {
    "execution": "...",
    "id": "...",
    "coldstart": true,
    "duration": 123.456,
    "billed_duration": 200,
    "coldstart_duration": 100,
    "timeout": 5000,
  },
  "system.memory.total": 536870912,
  "system.memory.actual.free": 0,
}

Later, the faas.* and system.* fields will be aggregated in transaction metrics. This should ideally be generalised to request-scoped metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws-λ-extension AWS Lambda Extension enhancement New feature or request v8.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants