Nucleus Researchが最近実施した2つの研究調査から、Elastic Cloudをデプロイした調査対象企業の満足度が極めて高いことが明らかになりました

blog-thumb-cloud-midnight.png

Leveraging Elastic to improve data management and observability in the cloud

Elastic導入で向上するクラウドのデータ管理とオブザーバビリティ

Ten times faster at a fraction of the cost. That's what a Forrester Total Economic Impact (TEI) study found about the value organizations can realize by deploying Elastic Observability and Security.

Ten times faster at a fraction of the cost.
If you want a headline as to why you should consider adopting Elastic for security and observability, that is it.&nbsp;
We often work with our customers to help them establish the business value of Elastic within their organizations. We commissioned Forrester to conduct a <a href="/elastic-stack/2021-total-economic-impact-elastic-observability-security/">Total Economic Impact (TEI) study of our security and observability solutions</a> so our customers have an unbiased view that they can share with their internal stakeholders. The TEI examines the ROI organizations realize by deploying the Elastic Observability and Security solutions.&nbsp;
This study showcases the incredible value that our customers are achieving and provides guidance to help you consider the costs, benefits, and business impact Elastic can bring to your organization.&nbsp;
The TEI study examined how Elastic customers have benefited from using Elastic Observability and Security. It found that from all levels of an organization, Elastic users are realizing:&nbsp;
<ul> 
	<li aria-level="1">Up to 10X performance improvement and 75% reduction in licensing costs</li> 
	<li aria-level="1">358% ROI across Elastic Observability and Security&nbsp;</li> 
	<li aria-level="1">$19 million in quantified benefits across six different benefit value categories</li> 
	<li aria-level="1">Nearly $15 million in net benefits (after costs) across those same benefit categories</li> 
	<li aria-level="1">Less than a six-month payback period of the initial investment</li>
</ul><figcaption><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltfc97ebe470187d49/60bfe553971f487708eb213b/blog-total-economic-impact.png" data-sys-asset-uid="bltfc97ebe470187d49" alt="blog-total-economic-impact.png"> </figcaption><figcaption>Quantified benefits of Elastic observability and security</figcaption>At the highest level, the customers interviewed explained that Elastic is faster and more cost effective than their previous solutions. But also, the areas of quantified benefits, shown in the image above, deliver compelling business impact through direct and indirect business value from software and hardware savings as well as people and process improvements.&nbsp;
<h2>Observability and security monitoring team savings</h2>The study revealed that teams using Elastic found savings of nearly $2.1 million in reduced operations monitoring labor costs for observability and more than $585,000 in reduced operations and labor costs for security.&nbsp;

<blockquote>“We call our forecasting mechanism, ‘pre-mortem,’ identifying developing problems days to months in advance of when they would actually occur if we didn’t have Elastic’s ML. Our service level is 99.999%.” – Manager of streaming service monitoring, telecommunications
</blockquote><blockquote>“We have been able to reduce false positives significantly, probably around 60%. There are a couple of reasons: backtesting is very easy, so it is easier to tune the rules, and the detection logic is easy to write.” – Detection engineering lead, technology
</blockquote><ul>
</ul><h2>Impact on productivity and efficiency</h2>In addition, there were many productivity enhancements found across both observability and security. Observability customers found $3.1 million in increased developer productivity. Security customers saw a significant reduction in risk associated with data breaches, equivalent to $6.5 million in savings.&nbsp;

<blockquote>“We enabled our developers to prepare their own logs within Elastic and monitor what they are interested in. Developers frequently create a targeted dashboard and pass it on to the operations team when it goes to production – a win-win!!! Their involvement has really enabled us to move from being reactive to being proactive. As a result, we have been able to shorten release cycles. We have monitoring enabled at all levels of the release cycle, so we find errors at a very early stage and get them fixed. Continuous integration and delivery are much better due to Elastic.” – Manager of streaming service monitoring, telecommunications
</blockquote><blockquote>“The time it takes to identify root cause has gone down about 80%, be it small threats or one that requires weeks to investigate. It not only takes less time to determine what happens, but we have a more precise understanding of the threat, too.” – Detection engineering lead, technology
</blockquote><h2>Learn how Elastic can help your business</h2>There are numerous other quotes and details within the study about additional business value uncovered with Elastic as an observability and security platform. We encourage you to read the full study to understand all of them. No matter where you are on your journey, we want to help you achieve your goals. <a href="/elastic-stack/2021-total-economic-impact-elastic-observability-security/">Check out the Forrester TEI study</a>.

blog-banner-generic-elastic.png

blog-thumb-generic-elastic.png

Total Economic Impact™ study: Elastic delivers 10X performance with up to 75% cost savings

Total Economic ImpactTM study: Elastic delivers 10X performance with up to 75% cost savings

A deep dive into the Elastic Cloud Value Calculator calculations and assumptions. Use it to understand the details behind each benefit group, or leverage it to create your own version custom to your situation.

As your Elastic usage increases and your use cases expand, it's important to know the benefits and cost savings that you can achieve by running Elasticsearch as a service. But since every Elasticsearch implementation can vary by use case and deployment model, it can be complicated to tackle on your own.By understanding the business impact and efficiencies of Elastic Cloud you can determine if you're already on the right track.<h2>Reduce IT infrastructure and storage costs</h2>Cost savings usually start here, as it’s quite frequently the biggest bucket of potential value. Some of the factors this calculation takes into account are:<ul><li>What instance types (and their respective costs) are you running Elastic on?</li><li>What do those instances cost annually?</li><li>If you aren't on Elastic Cloud, are you using reserve or on-demand pricing?</li><li>If you're running Elasticsearch in your own data center, what is the three-year amortized value of the hardware?</li></ul>The first situation we filter for is whether you are running Elastic in your own data center or running it self-managed on a cloud provider. Each situation has its own infrastructure cost implications, which we break down below.<h4>Self-hosted in your own data center</h4>Reduce self-hosted server costs:# of nodes * annual cost per server (server purchase / 3 years)&nbsp;* 100% reduction of future server costNote: For self-hosted servers, we assume a 1:1 ratio of server to node. If you are using larger machines that can handle multiple nodes, you’ll need to divide the annual cost of a server by the number of nodes you are running on each server in order to get the appropriate cost comparison.Reduce server maintenance cost:# of nodes * 20% of annual server cost for maintenance &amp; support&nbsp;* 100% reduction of future server maintenance costNote: Maintenance of a server depends largely on the type of server and how old it is. Newer servers generally require less maintenance and support vs older ones (3+ years).Reduce data center overhead cost (heating, cooling, electric):# of nodes * 25% of annual server cost for infrastructure overhead&nbsp;* 100% reduction of future server maintenance costFor an overview of power usage associated with servers see this <a href="https://www.zdnet.com/article/toolkit-calculate-datacenter-server-power-usage/">ZD net article</a> on the topic.<h4>Self-hosted on another cloud provider</h4>Reduce cost of cloud services:# of nodes * annual cost per cloud virtual machine&nbsp;* 100% reduction of future cloud virtual machine costReduce cost of data transfer and storage (DTS):# of nodes * 20% of annual cloud virtual machine cost DTS&nbsp;* 100% reduction of DTS cost<h4>General benefits applied in both situations</h4>Reduce software licensing costs:# of nodes * 10% annual cost per server or cloud virtual machine&nbsp;* 100% reduction of future server license costNote: Assumptions&nbsp;here depend on whether you are using open source Linux, a RedHat distribution of the same, or something else for your server OS. Also, please keep in mind that this will be much higher if you are already paying for an Elastic licensed tier of software (Gold, Platinum, Enterprise) so you will need to take that into account and increase this amount if you are comparing self-managed to Elastic Cloud.<h3>Reduce overprovisioning cost of hardware</h3>We run into overprovisioned hardware on a regular basis. Whether you overestimated or are just planning for worst-case scenarios, Elastic Cloud can help you get your sizing right, regardless of the risks you need to mitigate. In addition, we just launched a new <a href="https://www.elastic.co/blog/autoscale-your-elastic-cloud-data-and-machine-learning-nodes">autoscaling capability</a> that will remove the need for you to ever have to worry about rightsizing your Elastic environment again when you use Elastic Cloud.Reduce overprovisioning cost of hardware:# of nodes * annual cost per server or cloud virtual machine&nbsp;* 22.5% reduction of future overprovisioning costsNote: We see ranges of overprovisioning usually between 15-30% of the total infrastructure required.<h3>Reduce unnecessary data duplication cost</h3>For the large community out there who are running Elastic self-managed on our free and open or Basic tiers, many will twist their deployment in order to reduce risk of exposure of data to the wrong audience. Often, the logical way to do this is to duplicate a portion of the data in your current Elastic cluster and put that portion of data in a new, isolated cluster for a specific audience. However, this effort can be reduced or eliminated by taking advantage of security and access controls, easily configured with Elastic Cloud.Reduce data duplication cost with access controls:[# of nodes * % of nodes duplicated (30% assumed without access controls)] * annual duplication cost per node (both infra and human capital costs) * 30% reduction of future duplication costsNote: We assume only 30% reduction in cost here in order to be conservative and to take into account the probability of this happening in all situations. If this is occurring in your situation, you should consider this improvement factor to be 100%.<h3>Subscription-level features</h3>Lastly, there are powerful features in our Enterprise tier that you only have access to as an Elastic customer, such as <a href="https://www.elastic.co/blog/whats-new-cloud-autoscaling-cross-cluster-search-data-tiers">searchable snapshots and data tiers</a>. The cold data tier enables you to run a single node of Elastic with the replica stored in durable object storage (Amazon S3, Azure Blob Storage, or Google Cloud Storage) to reduce replication cost. So you can still search the cold node, with snappy responsiveness, but with the backup being an ultra low-cost alternative. And that’s just the beginning. We’re currently working on a searchable frozen tier that sits entirely within object storage with an even more compelling cost profile.Reduce hardware cost with data tiering (not applied within model, but worth considering):# of nodes in warm data tier (assumes 50% of total nodes) * annual cost per server or cloud virtual machine * 50% reduction of future infrastructure costs through use of data tiers<h2>IT efficiency</h2>Running and administering the Elastic Stack can take time and personnel. Deployments often start small, with little administrative overhead. But as adoption increases, so does the implementation size, and so do the demands (and expectations) of your users. We are always working to make the administration easier from within Kibana, but there is a lot to keep in mind: shards, replicas, scaling, upgrading, security, compliance, capacity, and more. These are things that aren't necessarily considered the first time a cluster is spun up.Generally speaking, a 25-node cluster of Elastic for logging or observability will require about 50% of a person’s time to manage and orchestrate, based on anecdotal evidence and discussions with the many folks here at Elastic who have done the work. So to apply some logic to that, if 50 nodes = 1 DevOps full-time employee (FTE), then 1 node = 0.02 FTEs.But with Elastic Cloud, we frequently see 70% of that operational overhead removed from our administrators’ daily lives. Now you only need to take up a smaller fraction of someone's time per node, as Elastic Cloud takes care of many of the details. The ratio becomes 200 nodes to 1 FTE.If you want a better view into how we can divide and conquer the work together, have a look through <a href="https://www.elastic.co/cloud/shared-responsibility">our responsibility matrix</a>. The main responsibilities Elastic Cloud helps to make much easier include:<ol><li>Reducing overall DevOps automation required through predefined APIs and protocols. This broader category accounts for the lion’s share of the automation benefits to administrative teams. Reduce IT staff through Elastic Cloud orchestration: # of FTEs for running Elastic self managed on a node basis * $100,000 FTE * 70% reduction in FTE time required to manage Elastic </li></ol><ol start="2"><li>Reducing time to manage upgrades by 95%. Reduce time to manage upgrades: Number of upgrades per year (assume 2X as a starting point) * $3,200 per upgrade (64 hours) * 95% reduction in time for managing upgrades </li></ol><ol start="3"><li>Reducing risk of managing critical vulnerability incidents and associated costs to near zero. Reduce risk of critical vulnerability incidents: # of critical vulnerabilities per year (assumes 4) * $4,000 per critical vulnerability engineering time (80 hours) * 10% reduction in critical vulnerability incidents</li></ol><h2>Revenue and employee disruption risk</h2>This value category is potentially the largest, depending on your situation. Let’s talk about what it means to your business to run a highly stable, scalable, and resilient service with Elastic central to your architecture.<h3>Employee disruption risk reduction</h3>This is the most common and important area of downstream user risk reduction. There are two big questions you need to consider here:<ol><li>How many people at your company are using Elastic today (in some form) based on your implementation?</li><li>What is the cost of employees not having access to your Elastic implementation?</li></ol>If it’s a security- or observability-related application, this could mean that your end users lack support when there is an urgent security or downtime risk-related incident that needs to be addressed. Ask yourself:<ul><li>What is the cost per minute of disruption and downtime?</li><li>Will a single failure cause a domino effect of failures?</li><li>If there's an outage, will the observability solution also fail?</li></ul>And maybe most importantly: How forgiving will stakeholders be when preventable infrastructure issues cause business outages?Improve end-user productivity through reduced risk of disruptions:# of employee end users of the solution * $100,000 per FTE * 1% improvement in end user productivityNote: This improvement factor assumption means that your end users would experience 1% less downtime due to solution disruption. We generally see higher downtime for internal employee-facing applications, and as a result chose this improvement factor. Keep in mind that your uptime improvement should be based on your current uptime service-level agreement (SLA).<h3>Revenue and service risk</h3>This calculation takes into account the risks associated with a customer-facing service you are running on Elastic. What is the risk of an outage associated with that service? Is there potential revenue at risk, and if so, how much?These are all good things to have a handle on, and we've made some simple assumptions for you if you choose this situation. Keep in mind that we generally apply this situation, conservatively, towards consumer-facing search use cases. For example, what would it mean if you are a retailer and your search stops working, and what is the cost of that possible outage? These are all risks that need to be considered and mitigated.Reduce risk of lost revenue due to unplanned downtime:Annual number of downtime hours (assume 44, or 99.5% uptime) * $25,000 per downtime hour * 90% reduction in downtime hoursNote:&nbsp;This improvement factor assumes an increase from 99.5% uptime to 99.95% uptime, an improvement of 90% as a starting point.<h3>Reduced risk of SLA violation</h3>This particular calculation is equally specific as the last one. The assumption is that you have embedded search or a related intelligence use case into a business customer-facing application. What’s the risk of your application experiencing instability that we can help you mitigate? And if your service-related search or lookup capability is down, will your end users claim they are experiencing an SLA violation? Anyone who's worked on a support contract knows how important these considerations are.Reduce risk of SLA violation:Annual SLA penalty events (we assume 1 to start) * [# of customers impacted by an SLA penalty event * average annual revenue per business customer * % of business customer revenue refunded due to penalty event (15% seeded)] * 20% reduction SLA penalty risk<h2>Security, risk, and compliance</h2>For these calculations, we don’t expose any inputs. Generally, this is an acknowledgement of the risk associated with running Elastic without the right security and compliance protocols in place. There is a very good reason to include these benefit calculations, even if your individual risk is marginally low. One must accept the fact that, without the right security setup — which comes standard with Elastic Cloud — Elastic users incur risk of collecting data and exposing that data. Sure, it can be cool to “move fast and break things,” but it isn’t sustainable in the long term when you take into account security and compliance concerns.Reduce cost of creating compliant solutions:Number of compliant solutions required (assumes 1) * cost per compliance solution (assumes $25,000) * 100% reduction in cost of creating and maintaining a compliance solutionReduce risk of data breach through use of access controls:[Risk of data breach in scope 1.2% (24% risk of data breach caused by human error: IBM research) * 5% chance of data breach associated with Elastic (vs other datastores)] * average cost per data breach (used industry benchmark from IBM of $8.1M) * 95% reduction in risk of data breach through use of access controlsReduce risk of downtime for regulated services:Downtime instances leading to regulatory violations (assumes 1) * average fine for regulated services (assumes $10,000) * 90% reduction in downtimeThese assumptions are similar to the reduced risk of downtime noted in the revenue and employee disruption risk section above.<h2>Learn how Elastic Cloud customers are realizing business value</h2>Many customers have migrated to Elastic Cloud to reduce costs, improve productivity, and enhance the availability of their deployments. Learn how a <a href="https://www.elastic.co/global-telecom-provider-realized-283-percent-roi-with-elastic-cloud">multinational telecom provider realized a 283% ROI after deploying Elastic Cloud for Elastic Observability</a>.Originally published March 15, 2021; Updated February 22, 2024.The release and timing of any features or functionality described in this post remain at Elastic's sole discretion. Any features or functionality not currently available may not be delivered on time or at all.

blog-banner-magnifying-glass-money-bag.jpg

blog-thumb-magnifying-glass-money-bag.jpg

Understand the business value of Elastic Cloud

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

headshot-ben-pruden-300x300.jpg

Ben Pruden

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Communication Preferences - ONLY for /communication-preferences

送信することにより、Elasticの<a href="/jp/legal/elastic-cloud-account-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、上記で提供された連絡先に<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">特定の通知</a>が送信されることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシーポリシー</a>をご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.By submitting this form, I agree to Elastic sharing my contact information with Google Cloud. I also agree to Elastic giving my information to the vendor for the purpose of shipping my food package.

GDPR Text + Google Cloud

送信することにより、Elasticの<a href="/jp/legal/elastic-cloud-account-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。このフォームを送信することにより、Elasticが私の連絡先情報をGoogle Cloudに共有することに同意します。また、Elasticが私に食材パッケージを発送する目的で私の情報をベンダーに提供することにも同意します。

By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Serverless GDPR Text

送信することにより、Elasticの<a href="/jp/legal/serverless-preview-terms" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.

Cloud Trial GDPR Text

送信することにより、<a href="/jp/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud利用規約</a>に同意したものとみなされます。個人情報は<a href="/jp/legal/privacy-statement">Elasticのプライバシーポリシー</a>に基づいて取り扱われます。

By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Newsletter GDPR Text

送信することにより、Elasticの<a href="/jp/legal/terms-of-use" target="_self">利用規約</a>を読み、同意したものと見なされます。また、関連する製品やサービスについて、上記で提供された情報を使用してElasticから<a href="/jp/legal/privacy-statement#how-we-use-the-information" target="_self">連絡する</a>場合があることを認めたことになります。詳細については、<a href="/jp/legal/privacy-statement/" target="_self">Elasticのプライバシー</a>ポリシーをご覧ください。これらの同意についてはいつでもオプトアウトすることが可能です。

Explore similar demos

Overview

Speakers

Close

See more insights

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

The content on this page is not available in the selected language.

このページのコンテンツは、選択された言語ではご利用いただけません。Elasticでは現在、コンテンツをさまざまな言語でご利用いただけるよう取り組んでいます。お使いの言語が準備されるまでお待ちくださるようお願いいたします。

Author

Articles by

Watch now (no PT)

Watch now

See all top stories

すべてのトップストーリーを見る

All (no PT translation)

Contact information

Press Release

Share on Reddit

Share this story

Share by Email

Thank you for your interest!

Contact Info

Follow us on Youtube

Load More

Share on LinkedIn

Search Integrations

All Solutions

Video for

See when this webinar starts in my time zone

現在のタイムゾーンでこのウェビナー開始時間を見る

Register to Watch

See All Posts

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

他の予定と重なってしまった…という場合も、問題ありません。参加登録されると、録画配信をご利用いただけます。関連コンテンツのご案内もメールでお届けします。

著者

記事執筆者 Ben Pruden

Elastic導入で向上するクラウドのデータ管理とオブザーバビリティ

Total Economic Impact^TM study: Elastic delivers 10X performance with up to 75% cost savings

Understand the business value of Elastic Cloud