As COVID-19 continues to make clear, being adaptable and resilient when the world changes can help a business stay alive. At Elastic, we know from experience that being distributed helps build a strong company that can scale and adapt as new challenges arise. In the spirit of open source and our relationship with the Elastic community, we’ve been offering tips and tricks on our blog and on social media about how to work effectively while remote.
A classic problem that every backend developer has faced during their work is testing an application that uses a database. A perfectly valid solution is to use the real database for testing your application, but you would be doing an integration test, while you want a unit test. There are many ways to solve this problem. You could create the database with docker, or use an in-memory compatible one, but if you are writing unit tests that can be easily parallelized this will become quite uncomfortable.
We are offering a variety of on-demand Elastic training courses for free — featuring 11 titles that span observability, security, and Elastic Stack administration. If you haven’t tried one of our self-paced courses yet, now is the perfect time to find out why so many people have shifted their learning preference from in-class to online. Our on-demand courses provide the same immersive learning experience found in the classroom, but delivered in a convenient, remote environment.
When working with observability data, a good portion of it comes in as time series data — things like CPU or memory utilization, network transfer, even application trace data. And the Elastic Stack offers powerful tools within Kibana for time series analysis, including TSVB (formerly Time Series Visual Builder). In this blog post, I’m going to attempt to demystify rates in TSVB by walking through three different types: positive rates, rate of change, and event rates.
Elasticsearch allows you to store, search, and analyze large amounts of structured and unstructured data. This speed, scale, and flexibility makes the Elastic Stack a powerful solution for a wide variety of use cases, like system observability, security (threat hunting and prevention), enterprise search, and more. Because of this flexibility, effectively architecting your deployment’s data storage for scale is incredibly important.
Confession: I am a security practitioner. I am also a mom. What I am not is a homeschool teacher. Earlier this year, I spoke to the 5th- and 6th-grade classes at my son’s Innovation Day about cybersecurity. I discussed what it means to be a cybersecurity practitioner and how the practice of cybersecurity affects everyday life.
Many mature security teams look to the MITRE ATT&CK® matrix to help improve their understanding of attacker tactics, techniques, and procedures (TTPs) and to better understand their own capabilities relative to these common adversarial approaches. With the release of Elastic Security 7.6, Elastic SIEM saw 92 detection rules for threat hunting and security analytics aligned to ATT&CK.
We’re excited to announce the release of Elastic Cloud Enterprise (ECE) 2.5! This release improves the experience of managing your deployments with a dedicated coordinating layer, support for snapshot lifecycle management (SLM), and more.
Open source software development can have a reputation for abrasive behavior. The search community is a clear counterexample for me, with a culture that emphasizes respect and acceptance. This culture played an important part in my own path to open source development. A little over six years ago, I was a wide-eyed software engineer settling into my first full-time job.
If your organization is like virtually every other in the world (including ours!), you use a mix of Microsoft products in your productivity stack, possibly including SharePoint, Office 365 and OneDrive. But you probably also rely on a variety of other applications, maybe even mingling in “competing” tools like G Suite or Dropbox, in addition to complementary tools like Zendesk or GitHub.
