|
| 1 | +--- |
| 2 | +products: |
| 3 | + - id: elasticsearch |
| 4 | + - id: elastic-stack |
| 5 | + - id: observability |
| 6 | + - id: security |
| 7 | +applies_to: |
| 8 | + serverless: |
| 9 | + stack: |
| 10 | +description: Choose the right Elastic solution for your organization. Compare search, observability, and security use cases to identify the best starting point for your trial. |
| 11 | +--- |
| 12 | + |
| 13 | +# Choose your use case |
| 14 | + |
| 15 | +Choosing the right use case for your trial is crucial to demonstrating value quickly. Elastic offers three primary solutions, each designed for specific organizational needs. This guide helps you identify which solution best addresses your immediate challenges. |
| 16 | + |
| 17 | +## Quick decision guide |
| 18 | + |
| 19 | +Answer these questions to identify your primary use case: |
| 20 | + |
| 21 | +| Question | Use case | |
| 22 | +|----------|----------------| |
| 23 | +| Do you need to build search experiences for users or search large volumes of data? | **Search** | |
| 24 | +| Are you troubleshooting application performance, system health, or infrastructure issues? | **Observability** | |
| 25 | +| Do you need to detect, investigate, or respond to security threats? | **Security** | |
| 26 | +| Are you trying to understand user behavior or analyze business data? | **Search** or **Observability** | |
| 27 | +| Do you need to monitor compliance or audit access to systems? | **Security** | |
| 28 | + |
| 29 | +## Solution overview |
| 30 | + |
| 31 | +### Elasticsearch (Search) |
| 32 | + |
| 33 | +**Best for**: Building search experiences, analyzing business data, and gaining insights from large datasets. |
| 34 | + |
| 35 | +**Common use cases**: |
| 36 | +- Website or application search |
| 37 | +- E-commerce product catalogs |
| 38 | +- Enterprise knowledge management |
| 39 | +- Log and event search |
| 40 | +- Business analytics and dashboards |
| 41 | +- Full-text search across documents |
| 42 | + |
| 43 | +**Your organization might need this if**: |
| 44 | +- Users struggle to find information across multiple systems. |
| 45 | +- You need to search and analyze large volumes of unstructured data. |
| 46 | +- You're building an application that requires fast, relevant search. |
| 47 | +- You want to create custom analytics dashboards for business data. |
| 48 | + |
| 49 | +**What you'll build in your trial**: |
| 50 | +- A searchable index of your data (documents, products, or events). |
| 51 | +- Custom search queries with filters and relevance tuning. |
| 52 | +- Basic analytics and visualizations. |
| 53 | +- A simple search interface or dashboard. |
| 54 | + |
| 55 | +**Time to value**: See search results within 1-2 hours of ingesting data. |
| 56 | + |
| 57 | +### Elastic Observability |
| 58 | + |
| 59 | +**Best for**: Monitoring applications, infrastructure, and services to ensure reliability and performance. |
| 60 | + |
| 61 | +**Common use cases**: |
| 62 | +- Application performance monitoring (APM) |
| 63 | +- Infrastructure and container monitoring |
| 64 | +- Log aggregation and analysis |
| 65 | +- Service-level objective (SLO) tracking |
| 66 | +- Incident investigation and root cause analysis |
| 67 | +- Real user monitoring (RUM) |
| 68 | + |
| 69 | +**Your organization might need this if**: |
| 70 | +- Applications are slow or experiencing errors. |
| 71 | +- You have limited visibility into system performance. |
| 72 | +- Logs are scattered across multiple systems. |
| 73 | +- You need to meet SLAs or track system uptime. |
| 74 | +- Troubleshooting incidents takes too long. |
| 75 | + |
| 76 | +**What you'll build in your trial**: |
| 77 | +- Monitoring for 2-3 key services or hosts. |
| 78 | +- Log aggregation from critical applications. |
| 79 | +- Performance dashboards and health metrics. |
| 80 | +- Alerting for important thresholds. |
| 81 | +- APM instrumentation for one application. |
| 82 | + |
| 83 | +**Time to value**: See metrics and logs within 30 minutes to 1 hour. |
| 84 | + |
| 85 | +### Elastic Security |
| 86 | + |
| 87 | +**Best for**: Detecting, investigating, and responding to security threats and vulnerabilities. |
| 88 | + |
| 89 | +**Common use cases**: |
| 90 | +- Security information and event management (SIEM) |
| 91 | +- Endpoint protection and detection (EDR) |
| 92 | +- Threat hunting and investigation |
| 93 | +- Vulnerability management |
| 94 | +- Security analytics and reporting |
| 95 | +- Compliance monitoring |
| 96 | + |
| 97 | +**Your organization might need this if**: |
| 98 | +- You need to detect and respond to security threats. |
| 99 | +- Security logs are difficult to analyze. |
| 100 | +- You want to monitor for suspicious activity. |
| 101 | +- Compliance requires security event tracking. |
| 102 | +- Incident response is manual and time-consuming. |
| 103 | + |
| 104 | +**What you'll build in your trial**: |
| 105 | +- Security data ingestion from key systems (endpoints, network, cloud). |
| 106 | +- Detection rules for common threats. |
| 107 | +- Security dashboards and timelines. |
| 108 | +- Alert workflows and case management. |
| 109 | +- Basic threat hunting capabilities. |
| 110 | + |
| 111 | +**Time to value**: See security events and detections within 1-2 hours. |
| 112 | + |
| 113 | +## Multi-solution approaches |
| 114 | + |
| 115 | +Many organizations benefit from multiple Elastic solutions working together. However, for your trial, we recommend starting with one primary use case to demonstrate clear value quickly. |
| 116 | + |
| 117 | +### Common combinations |
| 118 | + |
| 119 | +After your initial PoC, consider these complementary solutions: |
| 120 | + |
| 121 | +- Observability and Security: Monitor application health and detect security threats in the same platform. |
| 122 | +- Search and Observability: Build search experiences while monitoring application performance. |
| 123 | +- Security and Search: Search security events while maintaining threat detection capabilities. |
| 124 | + |
| 125 | +## Next steps |
| 126 | + |
| 127 | +After you've selected your use case: |
| 128 | + |
| 129 | +1. Review the solution documentation: |
| 130 | + - [Search documentation](/solutions/search.md) |
| 131 | + - [Observability documentation](/solutions/observability.md) |
| 132 | + - [Security documentation](/solutions/security.md) |
| 133 | + |
| 134 | +2. Continue to Week 1: [Week 1: Foundation and first use case](/get-started/trial-week-1.md) to start building your PoC. |
| 135 | + |
| 136 | +3. Set success criteria: Visit [Proof of concept framework](/get-started/trial-poc-framework.md) to define what success looks like for your organization. |
| 137 | + |
| 138 | +:::{tip} |
| 139 | +You can always expand to additional use cases after your initial PoC. Many successful Elastic implementations start with one solution and grow into comprehensive platforms that address multiple needs. |
| 140 | +::: |
| 141 | + |
| 142 | +## Need more guidance? |
| 143 | + |
| 144 | +- [Solutions overview](/get-started/introduction.md): Detailed comparison of all three solutions. |
| 145 | +- [Customer success stories](https://www.elastic.co/customers/success-stories): See how other organizations use Elastic. |
| 146 | +- [Contact sales](https://www.elastic.co/contact): Speak with a specialist about your specific needs. |
| 147 | + |
0 commit comments