In the wake of the COVID-19 pandemic, many organizations are adopting or experimenting with new models of long-term remote work. For some, that means keeping their teams fully distributed. For others, it means giving employees more flexibility to work from home or even simply putting plans in place for the future. But this shift to remote work brings new challenges that both large enterprises and smaller organizations must face.
As a developer I couldn’t imagine working without one of these three things. For projects on GitHub the built-in actions should do the latter job fine in most cases. But as everything else they have limits. The more PRs, the more different tests per pull request and the longer those tests run, the longer different PRs have to wait for each other for the continuous integration to run.
In January 2021, we announced that starting with version 7.11, we would be changing the Apache 2.0 portions of Elasticsearch and Kibana source code to be dual licensed under Elastic License and SSPL, at the users’ discretion. As part of that change, we created Elastic License 2.0 (ELv2) as a permissive, fair-code license, which allows free use, redistribution, modification, and derivative works, with only three simple limitations, outlined in our original announcement.
Creating an entity-centric index that contains only the latest document for each entity can be useful in a number of situations. For example, maybe you're managing an ecommerce site and you want to track the latest order placed by each of your customers. Or maybe you want to run a campaign targeting customers who haven't been active over a certain period. What's the fastest and most efficient way to compile and organize such data?
The move to cloud computing has been a no-brainer for many enterprise companies. But cloud computing is an expense that, unlike many other operating costs, is largely variable. Many companies — including the fastest-growing startups, largest enterprises, and leading government agencies — choose AWS to help them streamline fragmented processes, reduce costs, become more agile, and innovate faster.
Adding an API Gateway to your application is a good way to centralize some work you usually have to do for all of your API routes, like authentication or validation. But like every software system, it comes with its own problems. Solving errors in the cloud isn’t always straightforward, and API Gateway isn’t an exception. AWS API Gateway is an HTTP gateway, and as such, it uses the well-known HTTP status codes to convey its errors to you.
In our feature session for the current Enterprise Alert release, we were asked if it was possible to make the on-call page available to every employee regardless of whether they have a user account in Enterprise Alert or not. This option has existed in Enterprise Alert for a long time, but admittedly it is not very well documented. So I would like to take this opportunity to show you what the on-call overview can offer you and how to share the on-call page.
With the release of Enterprise Alert 9, not only have our capabilities for tighter integration with almost any source system imaginable been massively expanded, but our front end has also received some much requested updates. Among them are our multi-team schedules. These allow – especially for international companies – a simple and clear planning of readiness of several teams across different time zones.
