Skip to content
Merged
Show file tree
Hide file tree
Changes from 7 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions serverless/index-serverless-elasticsearch.asciidoc
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
[[what-is-elasticsearch-serverless]]
== {es}

== {es-serverless}
++++
<titleabbrev>{es}</titleabbrev>
++++
Expand Down
65 changes: 47 additions & 18 deletions serverless/pages/what-is-elasticsearch-serverless.asciidoc
Original file line number Diff line number Diff line change
@@ -1,32 +1,61 @@
////
To be rewritten/refined
////
// ℹ️ THIS CONTENT IS RENDERERED ON THE index-serverless-elasticsearch.asciidoc PAGE
// Use the id <<what-is-elasticsearch-serverless>> to link to this page

// :description: Build search solutions and applications with {es-serverless}.
// :keywords: serverless, elasticsearch, overview

preview:[]

{es} allows you to build custom applications. Whether you have structured or unstructured text, numerical data, or geospatial data, {es} can efficiently store and index it in a way that supports fast searches.

.Understanding {es-serverless}
[IMPORTANT]
[TIP]
====
Refer to <<elasticsearch-differences,Serverless differences>> and <<elasticsearch-technical-preview-limitations,Technical preview limitations>> for important details, including features and limitations specific to {es-serverless}.
If you haven't used {es} before, you might want to learn the basics in the https://www.elastic.co/guide/en/elasticsearch/reference/current/elasticsearch-intro.html[main {es} documentation].
====

[discrete]
== Get started
{es} is an open source distributed search and analytics engine, scalable data store, and vector database. It’s optimized for speed and relevance on production-scale workloads. Use {es} to search, index, store, and analyze data of all shapes and sizes.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this feels kinda weird because ES is also the foundation of obs and sec projects. could we reframe the ES project type as the "vanilla/search" option?

something like:

{es} is one of the three available project types on <<intro,{serverless-full}>>.

This project type lets you use the core functionality of {es}: Searching, indexing, storing, and analyzing data of all shapes and sizes.

and then let the es basics page take care of the "what is ES" question?

"lets you use" might feel restrictive - something like "is built for" "is optimized for"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nods in agreement, but on the "foundation of obs and sec projects" point I couldn't find a clean way to incorporate that info here but I'm also not too worried about that really

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cleared up intro in 040ebc5

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re: the foundational aspects we can revisit if it seems like people are creating additional projects in error


{es} is one of the three available project types on <<intro,{serverless-full}>>.

* <<elasticsearch-get-started,*Create your {es} project*>>: Create your first {es} project.
* <<elasticsearch-ingest-your-data,*Ingest your data*>>: Learn how to get your data into {es}.
When using {es} on {serverless-full} you don’t need to worry about managing the infrastructure that keeps {es} distributed and available: nodes, shards, and replicas. These resources are 100% automated on the serverless platform, which is designed to scale up and down with your workload.

This allows you to focus on building your search applications and solutions, without worrying about the underlying infrastructure.

[discrete]
== How to
[[elasticsearch-overview-get-started]]
== Get started

[cols="2"]
|===
| 🚀
a| [.card-title]#<<elasticsearch-get-started,*Create project →*>># +
Get started by creating your first {es} project on serverless.

* <<elasticsearch-search-your-data,*Search your data*>>: Build your queries to perform and combine many types of searches.
* <<elasticsearch-explore-your-data,*Explore your data*>>: Search, filter your data, and display your findings.
* <<elasticsearch-explore-your-data-alerting,*Manage alerts*>>: Create rules to detect complex conditions and trigger alerts.
* <<elasticsearch-dev-tools,*Use developer tools*>>: Send requests with Console and profile queries with Search Profiler.
* <<elasticsearch-manage-project,*Manage your project*>>: Manage user access, billing, and check performance metrics.
| 🔌
a| [.card-title]#<<elasticsearch-get-started,*Connect to {es} →*>># +
Learn how to connect your applications to your {es-serverless} endpoint.

// TODO add coming link to new page about connecting to your serverless endpoint
// <<elasticsearch-connecting-to-es-serverless-endpoint,*Connect your application →*>>

| 🔄
a| [.card-title]#<<elasticsearch-ingest-your-data,*Ingest data →*>># +
Learn how to get your data into {es} and start building your search application.

| 🛝
a| [.card-title]#https://www.elastic.co/guide/en/kibana/master/playground.html[*Try Search Playground →*]# +
Once you've added some data, use the Search Playground to test out queries and combine {es} with the power of Generative AI in your applications.
|===

[discrete]
[[elasticsearch-overview-learn-more]]
== Learn more

[cols="2"]
|===
| ❓
a| [.card-title]#<<elasticsearch-differences,*What's different on serverless? →*>># +
Understand the differences between {es} on {serverless-full} and other deployment types.

| 🧾
a| [.card-title]#<<elasticsearch-billing,*Billing →*>># +
Learn about the billing model for {es} on {serverless-full}.
|===