Markley Group is a Boston-based data center leader that provides co-location and private cloud services through a three-million square foot data center portfolio. The company was founded in 1991, when there was no such thing as the cloud. Today, many of its customers are experimenting in public cloud but often have workload requirements which are better suited or more affordable running on private infrastructure, according to Patrick Houston, Director of Engineering at Markley Group.

As work from home has ballooned in 2020, virtual methods for communicating with colleagues have become more critical than ever. Same goes for all the useful productivity and collaboration tools at our disposal. The emerging downside is the difficulty of finding needed information among so many tools. Compounding the problem is the tendency for info to get siloed off by department.

The client in consideration is one of the largest engineering, procurement, and construction (EPC) companies in India. With projects covering over 14 states in the country, its portfolio of services and offerings is widely diversified. It primarily engages in three forms of businesses – civil construction, road & highway development, and manufacturing.

Javascript is a pretty prolific programming language, used daily by people visiting any number of websites and web applications. NodeJS, it’s server-side version, is also used all over the place. You’ll find it deployed as full application stacks to functions in things like AWS Lambda, or even as IoT processes with things like Johnny Five. So when we think about Observability in the context of a nodejs stack, how do we set it up and get the information flowing?

These release notes describe new features, improvements and fixed issues in Pandora FMS NG 748. They also provide information about upgrades and describe some workarounds for known issues.

In this blog post series, I’ve explored the relationship between observability and a set of software delivery lifecycle practices that help organizations adopt DevOps practices and change their ways of working from being project centric to product-centric. I started with Site Reliability Engineering, then considered Value Stream Management (VSM) and finish with this post on Continuous Integration and Delivery (CI/CD). Defining Continuous Integration

Do you use an error tracking tool for your website? Have you ever tried to debug a problem that a user reported, and when you looked at your error tracking tool the reported error was simply: “Script Error”? Such errors are impossible to further debug because there is no additional information apart from that message.

Keeping track of what’s going on in Kubernetes isn’t easy. It’s an environment where things move quickly, individual containers come and go, and a large number of independent processes involving separate users may all be happening at the same time. Container-based systems are by their nature optimized for rapid, efficient response to a heavy load of requests from multiple users in a highly abstracted environment and not for high-visibility, real-time monitoring.

If you’re here, it means that your application is a hit, coming through a long way of development and deployments. Your application is finally in a stage where you or your team need to set up more servers than you can handle manually, and you have to provision them fast. There’s also the need to make sure that all of them have the same configuration, packages, and versions in order for your application to have the same behavior in all of them.

As you most likely know, Grafana Labs is growing. Growing like crazy! As Goutham Veeramachaneni noted in his blog post, “~30 people in March 2018 and now, in August 2020 we’re 180+ people. That is 6x growth in 2.5 years.” And we have no intention of slowing that growth. Matter of fact, we’re hiring as quickly as we can — and on top of that keep hiring specialists just to scale out hiring even more.