When discussing monitoring with IT and technical operations teams, it comes as no surprise that every team has its own parameters and requirements for their particular environment. Some teams just need an up-down of specific devices or interfaces, and others need more granular metrics like JVM or database performance. At the end of the day though, everyone is responsible for a service.
Engineering and “the business” don’t always speak the same language. That’s why in this blog post and webinar, we want to show you how to bridge the gap using the language “the business” understands: cold hard cash. When talking to the business value, here are four areas that DevOps provide value for your organization with associated calculators so you can get an exact value to share with your organization.
Go modules have helped bring order to Go development, but there’s been some disorder lurking. Managing module pseudo-versions can be difficult, especially with some of the latest changes to Go. JFrog GoCenter, the free repository of versioned Go modules, now includes some important updates that can help you stay on course. Let’s take a look at how pseudo-versions work, and what you can expect from those changes.
If you thought the fishmonger’s hair net was the only kind of net you’re wrong. From Pandora FMS we will show you some more, so that you do not get lost without them. The term “network” is used in computing to name a set of computers connected to each other in such a way that they can share resources, services, and information. There are several ways to classify these networks, based on their scope, relationship, or connection method.
Wherever people encounter a search bar — whether on Google, phone apps, or while shopping online — they're conditioned to expect search experiences that deliver fast and relevant results. With this ever-evolving expectation in mind, millions of developers and organizations have chosen Elasticsearch for building powerful content discovery experiences over the years, to the great delight of their audience and user base.
The current days of remote work and “IT Ops from home” may or may not be here to stay, but they definitely reinforce the need for consolidating and modernizing our monitoring. The challenges which multiple siloed tools create for understanding the big picture are only exacerbated by having just one screen to look at when monitoring our IT from our kitchen table.
Coronavirus (COVID-19) is greatly impacting the lives of organizations, employees and stakeholders. With the outbreak’s rising impact, more employees are migrating to remote, work-from-home practices as means of achieving “social distancing.” However, inevitable challenges are emerging with remote workdays. Obstacles include, but aren’t limited to, employee isolation, diminished productivity and poor team communication or collaboration.
SOLID is one of the most popular sets of design principles in object-oriented software development. All of them are broadly used and worth knowing. But in this first post of my series about the SOLID principles, I will focus on the first one: the Single Responsibility Principle.
Choosing the right OpenStack distribution is essential to the success of an OpenStack project at every organisation. When selecting one, organisations should always follow certain criteria. Is it possible to operate the considered OpenStack distributions economically? How easy is it to deploy them? Can the organisation upgrade its production OpenStack cloud without affecting the workloads? Everyone planning to deploy OpenStack should ask themselves these questions.
