In the last couple of decades, businesses have transformed from monolithic to service-oriented to microservices architecture. As a matter of fact, infrastructure has moved from physical servers to virtual machines to cloud and delivery models have changed from waterfall to agile to DevOps. This paradigm shift is being hailed as App Modernization.

At Splunk, we've been leading the way in observability and helping accelerate the adoption of the OpenTelemetry project. With the trace specification reaching a stable maturity level and several SignalFx Gateway and client library capabilities being upstreamed, we're ready to go all-in while we continue accelerating the growth and adoption of OpenTelemetry beyond the commitments we made last year.

Every business transformation needs a data strategy and the ability to manage increasingly complex environments. And while companies all over the globe are embracing the cloud, this shift has only exacerbated the associated complexity, compounded by the uncertainty brought about by the current global pandemic. You’ve got more data centers and attack surfaces to monitor and secure, in addition to greater unpredictability and risk.

Common Vulnerability Scoring System (CVSS) scores have been viewed as the de facto measure to prioritize vulnerabilities. Vulnerabilities are assigned CVSS scores ranging from one to 10, with 10 being the most severe. However, they were never intended as a means of risk prioritization. If you’ve relied on CVSS scores alone to safeguard your organization, here’s why you’re probably using them incorrectly.

Logs provide valuable information for troubleshooting application performance issues. But as your application scales and generates more logs, sifting through them becomes more difficult. Your logs may not provide enough context or human-readable data for understanding and resolving an issue, or you may need more information to help you interpret the IDs or error codes that application services log by default.

As the BFSI market gets more crowded, the only real differentiation available for businesses in this industry comes down to superior customer experiences. And this applies to both the internal teams and external customers. If the IT teams at the firm get the right type of support, they can work more efficiently and provide a seamless experience to the external customers.

Adopting SRE principles into your organization can be a big undertaking. You’ll need to develop new practices and procedures to minimize the costs of incident coordination. You’ll need to create a retrospective process that encourages continuous learning. You’ll need to shift culture to begin appreciating failure as an opportunity to grow. Your transition to the world of SRE will also require buy-in from all levels of your organization.

Surveys show that developers spend roughly 25% of their time troubleshooting issues, amounting to over one working day per week! Let’s examine the solutions that will guide your developers to the log insights they need to efficiently troubleshoot issues.

The latest Elasticsearch release version was made available on September 24, 2020 and contains several bug fixes and new features from the previous minor version released this past August. This article highlights some of the crucial bug fixes and enhancements made, discusses issues common to upgrading to this new minor version and introduces some of the new features released with 7.9 and its subsequent patches. A complete list of release notes can be found on the elastic website.

An Elastic Security Advisory (ESA) is a notice from Elastic to its users of a new Elasticsearch vulnerability. The vendor assigns both a CVE and an ESA identifier to each advisory along with a summary and remediation details. When Elastic receives an issue, they evaluate it and, if the vendor decides it is a vulnerability, work to fix it before releasing a remediation in a timeframe that matches the severity.