You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{kib}} lets you save objects for your own future use or for sharing with others. Each saved object type has different abilities. For example, you can save your search queries made with **Discover**, which lets you:
28
+
29
+
* Share a link to your search
30
+
* Download the full search results in CSV form
31
+
* Start an aggregated visualization using the same search query
32
+
* Embed the **Discover** search results into a dashboard
33
+
34
+
For organization, every saved object can have a name, [tags](tags.md), and type. Use the global search to quickly open a saved object.
35
+
36
+
## Manage saved objects
37
+
27
38
Edit, import, export, and copy your saved objects. These objects include dashboards, visualizations, maps, {{data-sources}}, **Canvas** workpads, and other saved objects.
28
39
29
40
You can find the **Saved Objects** page using the navigation menu or the [global search field](/get-started/the-stack.md#kibana-navigation-search).
The Elasticsearch platform and its UI, also known as Kibana, provide a comprehensive suite of tools to help you search, interact with, explore, and analyze your data effectively. These features empower you to gain deep insights, uncover trends, and take actionable steps based on your findings. This page is an overview of the key capabilities.
21
22
23
+
:::{dropdown} Accessibility statement
24
+
25
+
Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience, and strive toward ensuring our tools are usable by everyone.
26
+
27
+
28
+
**Measures to support accessibility**
29
+
Elastic takes the following measures to ensure accessibility of Kibana:
30
+
31
+
* Maintains and incorporates an [accessible component library](https://elastic.github.io/eui/).
32
+
* Provides continual accessibility training for our staff.
33
+
* Employs a third-party audit.
34
+
35
+
36
+
**Conformance status**
37
+
Kibana aims to meet [WCAG 2.1 level AA](https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl) compliance. Currently, we can only claim to partially conform, meaning we do not fully meet all of the success criteria. However, we do try to take a broader view of accessibility, and go above and beyond the legal and regulatory standards to provide a good experience for all of our users.
38
+
39
+
40
+
**Feedback**
41
+
We welcome your feedback on the accessibility of Kibana. Please let us know if you encounter accessibility barriers on Kibana by either emailing us at `[email protected]` or opening [an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29).
42
+
43
+
44
+
**Technical specifications**
45
+
Accessibility of Kibana relies on the following technologies to work with your web browser and any assistive technologies or plugins installed on your computer:
46
+
47
+
* HTML
48
+
* CSS
49
+
* JavaScript
50
+
* WAI-ARIA
51
+
52
+
53
+
**Limitations and alternatives**
54
+
Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Please [open an issue on GitHub](https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29) if you observe an issue not in this list.
55
+
56
+
Known limitations are in the following areas:
57
+
58
+
***Charts**: We have a clear plan for the first steps of making charts accessible. We’ve opened this [Charts accessibility ticket on GitHub](https://github.com/elastic/elastic-charts/issues/300) for tracking our progress.
59
+
***Maps**: Maps might pose difficulties to users with vision disabilities. We welcome your input on making our maps accessible. Go to the [Maps accessibility ticket on GitHub](https://github.com/elastic/kibana/issues/57271) to join the discussion and view our plans.
60
+
***Tables**: Although generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers and have poor captions. You will see incremental improvements as various applications adopt a new accessible component.
61
+
***Color contrast**: Modern Kibana interfaces generally do not have color contrast issues. However, older code might fall below the recommended contrast levels. As we continue to update our code, this issue will phase out naturally.
62
+
63
+
To see individual tickets, view our [GitHub issues with label "`Project:Accessibility`"](https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility).
64
+
65
+
66
+
**Assessment approach**
67
+
Elastic assesses the accessibility of Kibana with the following approaches:
68
+
69
+
***Self-evaluation**: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm that they are accessible.
70
+
***External evaluation**: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. Please email `[email protected]` if you’d like a copy.
71
+
***Automated evaluation**: We are starting to run [axe](https://www.deque.com/axe/) on every page. See our current progress in the [automated testing GitHub issue](https://github.com/elastic/kibana/issues/51456).
72
+
73
+
Manual testing largely focuses on screen reader support and is done on:
74
+
75
+
* VoiceOver on MacOS with Safari, Chrome and Edge
76
+
* NVDA on Windows with Chrome and Firefox
77
+
78
+
:::
79
+
22
80
## Querying and filtering
23
81
Elasticsearch’s robust query capabilities enable you to retrieve specific data from your datasets. Using the Query DSL (Domain Specific Language), you can build powerful, flexible queries that support:
24
82
@@ -48,24 +106,29 @@ Elasticsearch integrates machine learning for proactive analytics, helping you t
48
106
- Perform powerful NLP operations such as semantic search
49
107
- Machine learning models simplify complex predictive tasks, unlocking new opportunities for optimization.
50
108
51
-
## Discover
52
-
Discover lets you interact directly with raw data. Use Discover to:
109
+
## Explore with Discover [explore-the-data]
110
+
111
+
[Discover](/explore-analyze/discover.md) lets you interact directly with raw data. Use Discover to:
53
112
- Browse documents in your indices
54
113
- Apply filters and search queries
55
114
- Visualize results in real-time
56
115
57
116
It’s the starting point for exploratory analysis.
58
117
59
-
## Dashboards
60
-
Dashboards serve as centralized hubs for visualizing and monitoring data insights. With Dashboards, you can:
118
+
## Visualize the data [view-and-analyze-the-data]
119
+
120
+
Create a variety of visualizations and add them to a dashboard.
121
+
122
+
### Dashboards
123
+
[Dashboards](/explore-analyze/dashboards.md) serve as centralized hubs for visualizing and monitoring data insights. With Dashboards, you can:
61
124
- Combine multiple visualizations into a single, unified view
62
125
- Display data from multiple indices or datasets for comprehensive analysis
63
126
- Customize layouts to suit specific workflows and preferences
64
127
65
-
Dashboards provide an interactive and cohesive environment to explore trends and metrics at a glance.
128
+
Dashboards provide an interactive and cohesive environment with filtering capabilities and controls to explore trends and metrics at a glance.
66
129
67
-
## Panels and visualizations
68
-
Panels and visualizations are the core elements that populate your dashboards, enabling dynamic data representation. They support diverse chart types, Interactive filtering, and drill-down capabilities to explore data further. These building blocks transform raw data into clear, actionable visuals, allowing users to analyze and interpret results effectively.
130
+
###Panels and visualizations
131
+
[Panels and visualizations](/explore-analyze/visualize.md) are the core elements that populate your dashboards, enabling dynamic data representation. They support diverse chart types, Interactive filtering, and drill-down capabilities to explore data further. These building blocks transform raw data into clear, actionable visuals, allowing users to analyze and interpret results effectively.
69
132
70
133
## Reporting and sharing
71
134
You can share your work and findings with colleagues and stakeholders or generate reports. Report generation can be scheduled or on-demand. You can choose from multiple formats (for example, PDF, CSV). These tools ensure that actionable insights reach the right people at the right time.
@@ -75,3 +138,19 @@ You can set up alerts to monitor your data continuously. Alerts notify you when
75
138
## Bringing it all together
76
139
Elasticsearch's features integrate seamlessly, offering an end-to-end solution for exploring, analyzing, and acting on data. If you want to explore any of the listed features in greater depth, refer to their respective documentation pages and check the provided hands-on examples and tutorials.
77
140
141
+
If you'd like to explore some features but don't have data ready yet, some sample data sets are available in {{kib}} for you to install and play with.
142
+
143
+
### Add sample data [gs-get-data-into-kibana]
144
+
145
+
Sample data sets come with sample visualizations, dashboards, and more to help you explore {{kib}} before you ingest or add your own data.
146
+
147
+
1. Open the **Integrations** page from the navigation menu or using the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).
148
+
2. In the list of integrations, select **Sample Data**.
149
+
3. On the page that opens, select **Other sample data sets**.
150
+
4. Install the sample data sets that you want.
151
+
152
+
Once installed, you can access the sample data in the various {{kib}} apps available to you.
Copy file name to clipboardExpand all lines: explore-analyze/query-filter.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,10 @@ mapped_pages:
7
7
8
8
You can use {{es}} as a basic document store to retrieve documents and their metadata. However, the real power of {{es}} comes from its advanced search and analytics capabilities.
9
9
10
+
***{{es}} makes JSON documents searchable and aggregatable.** The documents are stored in an [index](/manage-data/data-store/index-basics.md) or [data stream](/manage-data/data-store/index-types/data-streams.md), which represent one type of data.
11
+
****Searchable* means that you can filter the documents for conditions.** For example, you can filter for data "within the last 7 days" or data that "contains the word {{kib}}". {{kib}} provides many ways for you to construct filters, which are also called queries or search terms.
12
+
****Aggregatable* means that you can extract summaries from matching documents.** The simplest aggregation is **count**, and it is frequently used in combination with the **date histogram**, to see count over time. The **terms** aggregation shows the most frequent values.
13
+
10
14
## Querying
11
15
12
16
You’ll use a combination of an API endpoint and a query language to interact with your data.
Combine free text search with field-based search using KQL. Type a search term to match across all fields, or start typing a field name to get suggestions for field names and operators that you can use to build a structured query. The semi-structured search will filter documents for matches, and only return matching documents.
19
+
20
+
|||
21
+
| --- | --- |
22
+
| Exact phrase query |`http.response.body.content.text:"quick brown fox"`|
| Range query |`account_number >= 100 and items_sold <= 200`|
26
+
| Wildcard query |`machine.os:win*`|
27
+
28
+
29
+
16
30
## Filter for documents where a field exists [_filter_for_documents_where_a_field_exists]
17
31
18
32
To filter documents for which an indexed value exists for a given field, use the `*` operator. For example, to filter for documents where the `http.request.method` field exists, use the following syntax:
0 commit comments