At the heart of RapidSpike is a development team who are passionate about pushing their abilities, learning new technologies and ultimately driving our software and product forward. We’ve researched and developed many cutting-edge features over the last 6 years but we’re shifting our focus this year. We’re taking a step back from new feature development in favour of upgrading, exploring and applying new technologies to existing functionality.
In today’s fast-paced digital world, your customers expect your services to be available 24 hours a day, seven days a week. If your services are unreliable, these customers will likely take their business elsewhere — and spread the word. To retain their business, you must understand and optimize your service and system health to ensure your services are reliable. Gauging your service and system health requires much more than knowing whether they’re on or off.
Service Accounts are "headless" Cloud 66 accounts - they are like team members that cannot log into the UI. They allow you to set up automation tasks or notifications that are not bound to a real person's account.
Time is invaluable. Besides being one of those can’t-argue-with universal truths, this is also one of the guiding principles behind Komodor; the promise behind our ‘troubleshooting efficiently and independently’ motto. ‘Pods Status and Logs’ is the latest of our timesaving features that enables you to quickly drill down in the pods of an unhealthy service, all from the comfort of your Komodor dashboard.
We recently attended the 2021 Cloud-Native Days Summit, where our co-founding CEO Ben Ofiri gave a lightning round talk on How to Troubleshoot Kubernetes With Confidence. In case you missed it, here’s a recording and transcript for your convenience.
At the moment I’m working at a tool for migrating Icinga 2 IDO history to Icinga DB . Sure, one could also run IDO and Icinga DB in parallel for one year and then switch to Icinga DB if they only care for the history of the past year. But the disadvantage is: one would have to wait one year. Nowadays (in our quickly changing world) that’s quite a long time.
While we know the many benefits of going serverless – reduced costs via pay-per-use pricing models, less operational burden/overhead, instant scalability, increased automation – the challenges of going serverless are often not addressed as comprehensively. The understandable concerns over migrating can stop any architectural decisions and actions being made for fear of getting it wrong and not having the right resources.
A WS is a comprehensive platform with over 200+ types of cloud services available globally. As organizations adopt these services, monitoring their performance can seem overwhelming. The majority of AWS workloads behind the scenes are dependent on a core set of services: EC2 (the compute service), EBS (block storage), and ELB (load balancing).
Thirty years ago today, Linus Torvalds announced his free operating system to the world. As with many of the world’s greatest, Linux had humble beginnings as a very small pet project. The GNU was working on an ambitious free, public domain operating system but the project had been delayed, and enthusiasts were quick to adopt Linus’ new project.
