[APM] Fix Otel missing fields undefined errors by jennypavlova · Pull Request #254271 · elastic/kibana

jennypavlova · 2026-02-20T17:27:08Z

Summary

This PR fixes uncaught errors when APM data has missing service or service.environment (e.g. OpenTelemetry or incomplete documents). The UI was reading error.service.environment, transaction.service.environment, and similar properties without optional chaining, causing "Cannot read properties of undefined (reading 'environment')" and error boundary crashes.

This PR:

Adds optional chaining and fallbacks to ENVIRONMENT_NOT_DEFINED / getEnvironmentLabel where service or environment may be missing
Updates error group details: error sample detail, contextual insight, and sample summary (optional error/service, safe access to error.error)
Updates transaction/span flyouts: transaction flyout, view full trace link, span flyout sticky properties
Updates agent configuration link: safe access to configService?.name and configService?.environment

How to test

Use APM with data that has no service or no service.environment (e.g. OTel or incomplete documents): If using synthtrace I added a scenario:
- Run node scripts/synthtrace missing_service_environment --from=now-1h --to=now+1h
- Confirm that the service.environment is not in the document and there is no error in the flyout:
Open error group details and an error sample, transaction flyout, span flyout, or a view that uses agent config service
Confirm the UI no longer crashes and shows "Not defined" (or equivalent) for missing environment where appropriate:

service_env_checks.mov

…ot-read-properties-of-undefined-reading-environment-otel-missing-serviceenvironment

elasticmachine · 2026-02-23T10:49:09Z

Pinging @elastic/obs-presentation-team (Team:obs-presentation)

elasticmachine · 2026-02-23T12:13:25Z

💚 Build Succeeded

Buildkite Build
Commit: 1c1e774

Metrics [docs]

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.7MB	2.7MB	+1.7KB

History

💔 Build #399105 failed 9a55399

cc @jennypavlova

smith · 2026-02-23T14:33:32Z

+/*
+ * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
+ * or more contributor license agreements. Licensed under the Elastic License
+ * 2.0; you may not use it except in compliance with the Elastic License 2.0.
+ */
+


Duplicate copywright

Suggested change

/*

* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one

* or more contributor license agreements. Licensed under the Elastic License

* 2.0; you may not use it except in compliance with the Elastic License 2.0.

*/

smith · 2026-02-23T14:34:13Z

+/*
+ * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
+ * or more contributor license agreements. Licensed under the Elastic License
+ * 2.0; you may not use it except in compliance with the Elastic License 2.0.
+ */
+


Duplicate copywright

Suggested change

/*

* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one

* or more contributor license agreements. Licensed under the Elastic License

* 2.0; you may not use it except in compliance with the Elastic License 2.0.

*/

smith

Verified the fix on an OTel service (flagd) with no service.environment — error sample detail page renders correctly, shows "Not defined" badge, no crash. Nice synthtrace scenario too.

smith · 2026-02-23T14:43:13Z

  };
 }
 export function SampleSummary({ error }: Props) {
-  const logMessage = error.error.log?.message;


Nit: ?.[0].message will throw if exception is an empty array — ?.[0] returns undefined, then .message throws. Should be ?.[0]?.message. Pre-existing issue (the original code had the same pattern), but since you're already touching this line it's a good time to fix it.

Suggested change

const logMessage = error.error.log?.message;

const excMessage = error?.error?.exception?.[0]?.message || error?.error?.message;

Good catch, thanks! fixed ✅

cauemarcondes

Synthtrace chages LGTM

kibanamachine · 2026-02-24T10:04:59Z

Starting backport for target branches: 8.19, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/22345992671

kibanamachine · 2026-02-24T10:13:10Z

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts
❌	9.2	Backport failed because of merge conflicts
❌	9.3	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 254271

Questions ?

Please refer to the Backport tool documentation

…ps-config-rebase * commit 'f135f030951237c5e9b0251931441aee3121b31d': (163 commits) [CPS] Support data view requests and do not sanitize project_routing in data plugin/resolve indices (elastic#253654) [One Workflow] Execute workflow from historical (elastic#253396) [streams][background tasks] gracefully handle non existing stream (elastic#254683) [Lens API] Waffle/Mosaic get green as a default color (elastic#254304) [Security Solution] Remove prebuilt rules customization callout on Rule Management page (elastic#254386) [Workflows] support passing attachments to run_agent step (elastic#251291) [One Discover][Logs UX] Update OpenTelemetry Semantic Conventions (elastic#254367) [kbn-es] Add --docker flag to yarn es snapshot (elastic#254306) [Workplace AI] Remove Data Source Config (elastic#254521) [Entity Store v2] Add CRUD API (elastic#252052) [CI] Increase type checking machine (elastic#254676) [main] Sync bundled packages with Package Storage (elastic#254232) Skip flaky test elastic#254625 (elastic#254662) Upgrade `@elastic/elasticsearch` to 9.3.1 (elastic#253660) [One Workflow] Migrate http step to new connector (elastic#249004) [Entity Store] Store EUID Scripts (elastic#254515) [APM] Fix Otel missing fields undefined errors (elastic#254271) [Console] Add support for documentation links on Serverless (elastic#254489) Create edit ILM flow (elastic#253393) [Agent Builder] Mid term: minimal recommended model set elastic#12875 (elastic#254560) ...

Closes elastic#254222 ## Summary This PR fixes uncaught errors when APM data has missing `service` or `service.environment` (e.g. OpenTelemetry or incomplete documents). The UI was reading `error.service.environment`, `transaction.service.environment`, and similar properties without optional chaining, causing "Cannot read properties of undefined (reading 'environment')" and error boundary crashes. This PR: - Adds optional chaining and fallbacks to `ENVIRONMENT_NOT_DEFINED` / `getEnvironmentLabel` where service or environment may be missing - Updates **error group details**: error sample detail, contextual insight, and sample summary (optional `error`/`service`, safe access to `error.error`) - Updates **transaction/span flyouts**: transaction flyout, view full trace link, span flyout sticky properties - Updates **agent configuration link**: safe access to `configService?.name` and `configService?.environment` ## How to test - Use APM with data that has no `service` or no `service.environment` (e.g. OTel or incomplete documents): If using synthtrace I added a scenario: - Run `node scripts/synthtrace missing_service_environment --from=now-1h --to=now+1h` - Confirm that the service.environment is not in the document and there is no error in the flyout: <img width="3446" height="1962" alt="image" src="https://github.com/user-attachments/assets/04867ef0-f89b-4601-b0bf-381a795ab2a6" /> - Open error group details and an error sample, transaction flyout, span flyout, or a view that uses agent config service - Confirm the UI no longer crashes and shows "Not defined" (or equivalent) for missing environment where appropriate: <img width="3456" height="1994" alt="image" src="https://github.com/user-attachments/assets/21fb7684-2c40-4eb5-b83d-063d9b2437be" /> https://github.com/user-attachments/assets/19c46cb3-ff2e-4938-8cf3-2316f7a1a4ae --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit f0e605f) # Conflicts: # x-pack/solutions/observability/plugins/apm/public/components/app/error_group_details/error_sampler/error_sample_detail.tsx

Closes elastic#254222 ## Summary This PR fixes uncaught errors when APM data has missing `service` or `service.environment` (e.g. OpenTelemetry or incomplete documents). The UI was reading `error.service.environment`, `transaction.service.environment`, and similar properties without optional chaining, causing "Cannot read properties of undefined (reading 'environment')" and error boundary crashes. This PR: - Adds optional chaining and fallbacks to `ENVIRONMENT_NOT_DEFINED` / `getEnvironmentLabel` where service or environment may be missing - Updates **error group details**: error sample detail, contextual insight, and sample summary (optional `error`/`service`, safe access to `error.error`) - Updates **transaction/span flyouts**: transaction flyout, view full trace link, span flyout sticky properties - Updates **agent configuration link**: safe access to `configService?.name` and `configService?.environment` ## How to test - Use APM with data that has no `service` or no `service.environment` (e.g. OTel or incomplete documents): If using synthtrace I added a scenario: - Run `node scripts/synthtrace missing_service_environment --from=now-1h --to=now+1h` - Confirm that the service.environment is not in the document and there is no error in the flyout: <img width="3446" height="1962" alt="image" src="https://github.com/user-attachments/assets/04867ef0-f89b-4601-b0bf-381a795ab2a6" /> - Open error group details and an error sample, transaction flyout, span flyout, or a view that uses agent config service - Confirm the UI no longer crashes and shows "Not defined" (or equivalent) for missing environment where appropriate: <img width="3456" height="1994" alt="image" src="https://github.com/user-attachments/assets/21fb7684-2c40-4eb5-b83d-063d9b2437be" /> https://github.com/user-attachments/assets/19c46cb3-ff2e-4938-8cf3-2316f7a1a4ae --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit f0e605f) # Conflicts: # src/platform/packages/shared/kbn-apm-synthtrace/src/scenarios/missing_service_environment.ts # x-pack/solutions/observability/plugins/apm/public/components/app/error_group_details/error_sampler/error_sample_detail.tsx

jennypavlova · 2026-02-24T15:26:50Z

💚 All backports created successfully

Status	Branch	Result
✅	9.3
✅	9.2
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

Closes elastic#254222 ## Summary This PR fixes uncaught errors when APM data has missing `service` or `service.environment` (e.g. OpenTelemetry or incomplete documents). The UI was reading `error.service.environment`, `transaction.service.environment`, and similar properties without optional chaining, causing "Cannot read properties of undefined (reading 'environment')" and error boundary crashes. This PR: - Adds optional chaining and fallbacks to `ENVIRONMENT_NOT_DEFINED` / `getEnvironmentLabel` where service or environment may be missing - Updates **error group details**: error sample detail, contextual insight, and sample summary (optional `error`/`service`, safe access to `error.error`) - Updates **transaction/span flyouts**: transaction flyout, view full trace link, span flyout sticky properties - Updates **agent configuration link**: safe access to `configService?.name` and `configService?.environment` ## How to test - Use APM with data that has no `service` or no `service.environment` (e.g. OTel or incomplete documents): If using synthtrace I added a scenario: - Run `node scripts/synthtrace missing_service_environment --from=now-1h --to=now+1h` - Confirm that the service.environment is not in the document and there is no error in the flyout: <img width="3446" height="1962" alt="image" src="https://github.com/user-attachments/assets/04867ef0-f89b-4601-b0bf-381a795ab2a6" /> - Open error group details and an error sample, transaction flyout, span flyout, or a view that uses agent config service - Confirm the UI no longer crashes and shows "Not defined" (or equivalent) for missing environment where appropriate: <img width="3456" height="1994" alt="image" src="https://github.com/user-attachments/assets/21fb7684-2c40-4eb5-b83d-063d9b2437be" /> https://github.com/user-attachments/assets/19c46cb3-ff2e-4938-8cf3-2316f7a1a4ae --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit f0e605f) # Conflicts: # src/platform/packages/shared/kbn-apm-synthtrace/src/scenarios/missing_service_environment.ts # x-pack/solutions/observability/plugins/apm/public/components/app/error_group_details/error_sampler/error_sample_detail.tsx

# Backport This will backport the following commits from `main` to `9.2`: - [[APM] Fix Otel missing fields undefined errors (#254271)](#254271)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

# Backport This will backport the following commits from `main` to `9.3`: - [[APM] Fix Otel missing fields undefined errors (#254271)](#254271)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

) # Backport This will backport the following commits from `main` to `8.19`: - [[APM] Fix Otel missing fields undefined errors (#254271)](#254271)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

Closes elastic#254222 ## Summary This PR fixes uncaught errors when APM data has missing `service` or `service.environment` (e.g. OpenTelemetry or incomplete documents). The UI was reading `error.service.environment`, `transaction.service.environment`, and similar properties without optional chaining, causing "Cannot read properties of undefined (reading 'environment')" and error boundary crashes. This PR: - Adds optional chaining and fallbacks to `ENVIRONMENT_NOT_DEFINED` / `getEnvironmentLabel` where service or environment may be missing - Updates **error group details**: error sample detail, contextual insight, and sample summary (optional `error`/`service`, safe access to `error.error`) - Updates **transaction/span flyouts**: transaction flyout, view full trace link, span flyout sticky properties - Updates **agent configuration link**: safe access to `configService?.name` and `configService?.environment` ## How to test - Use APM with data that has no `service` or no `service.environment` (e.g. OTel or incomplete documents): If using synthtrace I added a scenario: - Run `node scripts/synthtrace missing_service_environment --from=now-1h --to=now+1h` - Confirm that the service.environment is not in the document and there is no error in the flyout: <img width="3446" height="1962" alt="image" src="https://github.com/user-attachments/assets/04867ef0-f89b-4601-b0bf-381a795ab2a6" /> - Open error group details and an error sample, transaction flyout, span flyout, or a view that uses agent config service - Confirm the UI no longer crashes and shows "Not defined" (or equivalent) for missing environment where appropriate: <img width="3456" height="1994" alt="image" src="https://github.com/user-attachments/assets/21fb7684-2c40-4eb5-b83d-063d9b2437be" /> https://github.com/user-attachments/assets/19c46cb3-ff2e-4938-8cf3-2316f7a1a4ae --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

jennypavlova added 2 commits February 20, 2026 18:14

[APM] Fix the undefined environment issue

6bfce67

[APM] Fix other Otel incomplete data potential issues

cf0b7e0

jennypavlova self-assigned this Feb 20, 2026

jennypavlova added 2 commits February 23, 2026 11:21

[APM] Add synthtrace scenario without env and tests

1c346ad

Merge branch 'main' of github.com:elastic/kibana into 254222-apm-cann…

9a55399

…ot-read-properties-of-undefined-reading-environment-otel-missing-serviceenvironment

jennypavlova marked this pull request as ready for review February 23, 2026 10:37

jennypavlova requested review from a team as code owners February 23, 2026 10:37

jennypavlova added release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release Team:obs-presentation Focus: APM UI, Infra UI, Hosts UI, Universal Profiling, Obs Overview and left Navigation labels Feb 23, 2026

Changes from node scripts/eslint_all_files --no-cache --fix

1c1e774

smith reviewed Feb 23, 2026

View reviewed changes

smith approved these changes Feb 23, 2026

View reviewed changes

cauemarcondes approved these changes Feb 23, 2026

View reviewed changes

CR fixes

6647151

jennypavlova merged commit f0e605f into elastic:main Feb 24, 2026
17 checks passed

kibanamachine added the v9.4.0 label Feb 24, 2026

jennypavlova mentioned this pull request Feb 24, 2026

[9.3] [APM] Fix Otel missing fields undefined errors (#254271) #254748

Merged

jennypavlova mentioned this pull request Feb 24, 2026

[9.2] [APM] Fix Otel missing fields undefined errors (#254271) #254756

Merged

jennypavlova mentioned this pull request Feb 24, 2026

[8.19] [APM] Fix Otel missing fields undefined errors (#254271) #254758

Merged

kibanamachine added the v9.2.6 label Feb 24, 2026

kibanamachine added the v9.3.1 label Feb 24, 2026

kibanamachine added the v8.19.12 label Feb 24, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[APM] Fix Otel missing fields undefined errors#254271

[APM] Fix Otel missing fields undefined errors#254271
jennypavlova merged 6 commits intoelastic:mainfrom
jennypavlova:254222-apm-cannot-read-properties-of-undefined-reading-environment-otel-missing-serviceenvironment

jennypavlova commented Feb 20, 2026 •

edited by kibanamachine

Loading

Uh oh!

elasticmachine commented Feb 23, 2026

Uh oh!

elasticmachine commented Feb 23, 2026

Uh oh!

smith Feb 23, 2026

Uh oh!

smith Feb 23, 2026

Uh oh!

smith left a comment

Uh oh!

smith Feb 23, 2026

Uh oh!

jennypavlova Feb 24, 2026

Uh oh!

cauemarcondes left a comment

Uh oh!

Uh oh!

kibanamachine commented Feb 24, 2026

Uh oh!

kibanamachine commented Feb 24, 2026

Uh oh!

jennypavlova commented Feb 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

	const logMessage = error.error.log?.message;
	const excMessage = error?.error?.exception?.[0]?.message \|\| error?.error?.message;

Conversation

jennypavlova commented Feb 20, 2026 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

How to test

Uh oh!

elasticmachine commented Feb 23, 2026

Uh oh!

elasticmachine commented Feb 23, 2026

💚 Build Succeeded

Metrics [docs]

Async chunks

History

Uh oh!

smith Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

smith Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

smith left a comment

Choose a reason for hiding this comment

Uh oh!

smith Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

jennypavlova Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

cauemarcondes left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Feb 24, 2026

Uh oh!

kibanamachine commented Feb 24, 2026

💔 All backports failed

Manual backport

Questions ?

Uh oh!

jennypavlova commented Feb 24, 2026

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

jennypavlova commented Feb 20, 2026 •

edited by kibanamachine

Loading