ELK Implementation Assessment

ELK Implementation Assessment

Based on the answers you provide about your ELK environment and practices, this assessment will help you better understand how your ELK compares to your peers and how to make it more reliable, secure, and performant in production.

What
You
Get?

Recommendations Based on Your ELK Environment

Customized Infrastructure Costs

ELK Best Practices and Educational Materials

/14

Steven, Enter the primitive data types available in JavaScript.

  • 5 days
  • 14 days
  • 30 days
s
5GB
2TB

/14

Steven, Enter the primitive data types available in JavaScript.

/14

Steven, Enter the primitive data types available in JavaScript.

Your results are ready

Fill in your details to get the customized PDF with your infrastructure costs, recommendations and best practices.

Your ELK Infrastructure Costs

ELK Performance & Reliability at Scale

Security & Compliance

Next

logo
main

ELK
Implementation
Assessment
results

Your ELK Infrastructure Costs

30 days

1 TB

Queing Server (Redis, RabbitMQ, Kafka)

6 m5.2xlarge instances

Queing Server Cluster Management (Zookeeper?)

6 m5.2xlarge instances

Logstash

6 m5.2xlarge instances

Elasticsearch Data (min of 2)

6 m5.2xlarge instances

Elasticsearch Master

6 m5.2xlarge instances

Elasticsearch Client

6 m5.2xlarge instances

Kibana Server

6 m5.2xlarge instances

Total:

6 m5.2xlarge instances

How experienced are you with the ELK Stack?

Some expirience

Logz.io recommendation

text

How do you know when something in your ELK Stack is broken?

Some expirience

Logz.io recommendation

text

Do you index your application logs?

Some expirience

Logz.io recommendation

text

How experienced are you with log parsing?

Some expirience

Logz.io recommendation

text

Are you filtering out any of your log data before it's indexed?

Some expirience

Logz.io recommendation

text

Does your environment generate volatile volumes of log data?

Some expirience

Logz.io recommendation

text

Do complex queries cause poor performance or even failures?

Some expirience

Logz.io recommendation

text

Should your log volumes grow in the coming year, do you have a plan for scaling your Elasticsearch cluster(s)?

Some expirience

Logz.io recommendation

text

How do you manage your Elasticsearch indices?

Some expirience

Logz.io recommendation

text

Do you want to use the most recent, stable, and secure versions of ELK Stack components?

Some expirience

Logz.io recommendation

text

Does your log data contain sensitive information?

Some expirience

Logz.io recommendation

text

Can anyone in your organization access your log data? Or is that a security risk?

Some expirience

Logz.io recommendation

text

Does your log data and log management system need to be in compliance with industry or national regulations (PCI, GDPR, HIPAA, SOC 2, ect.)?

Some expirience

Logz.io recommendation

text

What are you willing to dedicate to your ELK Stack?

You’ve probably heard of Netflix, Facebook, and LinkedIn, right? All these companies are running their own ELK Stacks, as are thousands of other very successful companies. So, running ELK on your own is definitely possible. But it's important to be prepared for what it entails. These companies have massive teams capable of handling the burden of scaling ELK deployments. The question to ask yourself is whether your team has the time and resources to scale ELK on your own. If you’re unsure whether you have the resources needed to run a reliable, secure, and performant ELK at scale, a managed solution might be a better option for you. Logz.io delivers the ELK Stack as a fully managed service. This means you can continue using the ELK Stack you know, without the overhead of all these best practices, resources, and costs required to do it yourself.