IT spending grew to an impressive $3.8 trillion in 2019. With 2020 giving enterprises a reality check on remote working, the spending on digital transformation is expected to grow even further. It goes without saying that IT is an integral part of any company, big or small. When the stakes are so high, there’s very little room for mistakes. However, we’re all humans and do make mistakes.
Logging solutions are a must-have for any company with software systems. They are necessary to monitor your software solution’s health, prevent issues before they happen, and troubleshoot existing problems. The market has many solutions which all focus on different aspects of the logging problem. These solutions include both open source and proprietary software and tools built into cloud provider platforms, and give a variety of different features to meet your specific needs.
If you’ve already connected your GitHub integration via OAuth in GitKraken, you’re good to go! GitHub is changing its security policy and will no longer allow username/password-only access. This change goes into effect on August 13th, 2021, and affects all desktop Git applications that offer a GitHub integration, including GitKraken. Users who have already authenticated to GitHub using OAuth will be unaffected. OAuth is the default connection method within your GitKraken profile settings.
One of the biggest reasons organizations don’t try out a new software vendor is the perceived costs of switching. Most cite the fear of implementation being too expensive, too difficult, or too time-consuming—all excuses to justify maintaining a vendor contract, even if that vendor is performing poorly and not meeting expectations. But what’s at risk when organizations simply renew year after year? Who loses if the status quo is maintained?
It has been just over two years since we introduced the Elastic Common Schema (ECS), and what a journey it’s been. From categorization fields to request for comments to Threat Intelligence fields, ECS has evolved rapidly over the course of the last two years. In this blog post, I would like to reflect on the ECS journey so far, and look towards the future of ECS.
With so many IT vendors claiming they provide AIOps platforms, how do you understand the differences between them, and decide what flavor of AIOPs to choose for your organization? Join us in a CTO Perspective discussion with Elik Eizenberg, CTO and co-founder at BigPanda, to find the answer. Read the skinny for a brief summary, then either lean back and watch the interview, or if you prefer to continue reading, take a few minutes to read the transcript. Enjoy!