Operations | Monitoring | ITSM | DevOps | Cloud

Alan and Lee talk about the journey of Cloudsmith, and how we got to where we're at today with the latest pricing announcement.

We dive into the details of why we're changing the pricing at Cloudsmith, what it means for you, and how we can help.

If you are on Shipa Cloud today, you will have noticed a new module called Insights. We are pleased to announce the initial release of Shipa Insights and certainly have a lot in store as we continue to build out the module. As more items continue to shift left towards the developer and the rise of the full lifecycle developer continues to occur, outside of technical non-functional requirements such as connectivity, reporting and metrics are also important.

Incident management is a practice that seeks to resolve business-impacting events in the most efficient manner possible. But not every problem that arises requires an incident response, and it’s crucial that teams know the difference between a problem and an incident. Responding to problems may be part of daily routines, or small ad hoc projects that don’t require more than one resource or a significant time commitment.

More often than not, as developers, when we get a report that a large customer is hitting 502 errors, there's a flurry of activity. What's wrong? Is something deeply broken? So you start digging through AWS logs to see what you can find, but it's hard to reproduce. Sometimes, there's no clear answer, and you move on without any resolution. What if I told you it doesn't have to be this way?

It’s been twenty years since the corporate scandals of Enron, WorldCom, and Tyco. The collapse of these giant corporations ruined the lives of the employees who tirelessly worked for leaders who let greed dictate their decision-making. Laws have been implemented since then to help reduce the risk of another Enron, but laws won’t stop all instances of poor leadership. Poor tone at the top increases vulnerabilities, employee non-compliance, and job dissatisfaction.