Operations | Monitoring | ITSM | DevOps | Cloud

The best way to stay out of danger is to keep far away from where danger lurks. But in the internet age, the global network means risk to your systems is from everywhere, at all times. With estimates that worldwide damage from cybercrime will exceed 6 trillion dollars by 2021, many companies choose, or are required by regulations to isolate their most sensitive systems to avoid any type of security breach.

At CloudZero, we talk to leadership teams at SaaS and companies every day. When it comes to individual customer profitability, the vast majority of them fall into two camps: they’re either taking their best guess — or they have no idea. Typically only the largest companies - those with the resources to dedicate a 5-10 person engineering team to calculating cost - have this level of insight. And you can be sure they yield that knowledge to their competitive advantage!

In the previous article, we have created the Continuous Integration (CI) pipeline for a simple Java application. It is now time to start working on the Continuous Deployment (CD) pipeline that will take the Java application and deploy it to AWS. To build the CD pipeline, we will extend the existing AWS Jenkins pipeline. If you have missed the previous article on building a CI pipeline for a Java application using Jenkins, make sure you read that first before continuing.

Do you need to integrate a new company in with your existing employer and therefore in to your already provisioned Azure AD tenant. Or perhaps just need to share your tenancy and office 365 services with more than one company, then you could find yourself in a position where you need to sync users from another domain and have already configured AD Connect, well there is a way to add the second domain to your current Azure tenancy, so you can sync those users from the second domain.

Monitoring Jenkins is a serious challenge. Logging is often overlooked, but it provides a wealth of information about the health of your Jenkins instance. The following are some approaches to generating informative logging to these issues, that can help to monitor and provide suitable explanations of where the problems lie; even identifying what the possible solutions are.

Your website is the face of your business - it should urge the customer to buy your product. Knowing this, you spend weeks on a great web design and user experience. But that’s only the visible part, what about your site’s infrastructure? In order to make your website as optimized as possible, you need metrics about everything such as customer behavior, load speeds, proxy request counts, load balancers and more.

The perception that Netdata is only capable of short-term metrics storage is a myth. It’s a pervasive myth we still see in blog posts and through community engagement, despite it being false for more than a year. However, like all myths, this one on metrics storage began with a kernel of truth. When Netdata first flourished as an open-source project in 2017 and 2018, the default metrics database was RAM-only.