|
2 | 2 | mapped_urls: |
3 | 3 | - https://www.elastic.co/guide/en/observability/current/apm-filters.html |
4 | 4 | - https://www.elastic.co/guide/en/serverless/current/observability-apm-filter-your-data.html |
| 5 | + |
| 6 | +navigation_title: "Filters" |
5 | 7 | --- |
6 | 8 |
|
7 | | -# Filter application data |
| 9 | +# Filter application data [apm-filter-your-data] |
| 10 | + |
| 11 | + |
| 12 | +Global filters are ways you can filter your APM data based on a specific time range or environment. When viewing a specific service, the filter persists as you move between tabs. |
| 13 | + |
| 14 | +:::{image} ../../../images/observability-global-filters.png |
| 15 | +:alt: Global filters view |
| 16 | +:class: screenshot |
| 17 | +::: |
| 18 | + |
| 19 | +::::{note} |
| 20 | +If you prefer to use advanced queries on your data to filter on specific pieces of information, see [Query your data](../../../solutions/observability/apps/use-advanced-queries-on-application-data.md). |
| 21 | + |
| 22 | +:::: |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +## Global time range [apm-filter-your-data-global-time-range] |
| 27 | + |
| 28 | +The global time range filter restricts APM data to a specific time period. |
8 | 29 |
|
9 | | -% What needs to be done: Align serverless/stateful |
10 | 30 |
|
11 | | -% Use migrated content from existing pages that map to this page: |
| 31 | +## Service environment filter [apm-filter-your-data-service-environment-filter] |
12 | 32 |
|
13 | | -% - [ ] ./raw-migrated-files/observability-docs/observability/apm-filters.md |
14 | | -% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-filter-your-data.md |
| 33 | +The environment selector is a global filter for `service.environment`. It allows you to view only relevant data and is especially useful for separating development from production environments. By default, all environments are displayed. If there are no environment options, you’ll see "not defined". |
15 | 34 |
|
16 | | -% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc): |
| 35 | +Service environments are defined when configuring your APM agents. It’s vital to be consistent when naming environments in your APM agents. To learn how to configure service environments, see the specific APM agent documentation: |
17 | 36 |
|
18 | | -$$$environment-selector$$$ |
| 37 | +* **Go:** [`ELASTIC_APM_ENVIRONMENT`](https://www.elastic.co/guide/en/apm/agent/go/current/configuration.html#config-environment) |
| 38 | +* **iOS agent:** *Not yet supported* |
| 39 | +* **Java:** [`environment`](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-environment) |
| 40 | +* **.NET:** [`Environment`](https://www.elastic.co/guide/en/apm/agent/dotnet/current/config-core.html#config-environment) |
| 41 | +* **Node.js:** [`environment`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#environment) |
| 42 | +* **PHP:** [`environment`](https://www.elastic.co/guide/en/apm/agent/php/current/configuration-reference.html#config-environment) |
| 43 | +* **Python:** [`environment`](https://www.elastic.co/guide/en/apm/agent/python/current/configuration.html#config-environment) |
| 44 | +* **Ruby:** [`environment`](https://www.elastic.co/guide/en/apm/agent/ruby/current/configuration.html#config-environment) |
| 45 | +* **Real User Monitoring:** [`environment`](https://www.elastic.co/guide/en/apm/agent/rum-js/current/configuration.html#environment) |
0 commit comments