Operations | Monitoring | ITSM | DevOps | Cloud

Over the last couple of weeks, we’ve prioritized some sustaining product goals to polish the codebase and update some big ticket dependencies. Among those updates were: React, Redux, and Webpack - the biggies. The first two were pretty painless and inspired the confidence to approach updating Webpack from v2 to v4 like maybe no big deal! Though confidence level was on high, I felt a slight chill and a twinge of doubt by the prospect of making changes to our build configs.

KubeCon + CloudNativeCon North America 2018 was an incredible event. We had many exciting announcements – LogDNA’s new partnership with IBM Cloud, our recent round of funding, as well as great conversations, product demos, fun giveaways, and even surprise gifts for loyal customers, our booth was jam packed.

Jenkins is an extremely popular, open-source, continuous integration tool used for running tests, building code, and subsequently pushing to staging and then production. In a previous post, I outlined instructions for collecting, analyzing and visualizing Jenkins system logs.

It’s hard to find time for DevOps in a startup when there’s so much else to do. Having a great idea is cool, you may already carved a plan, maybe even practiced some pitching and basically started working, you should be focusing on developing your product and doing that alone.

Thought you could wind down for the change freeze? Sorry, we’ve got one last thing for you to do: Upgrade StackStorm to 2.10! Orquesta is now ready for almost all workflow use-cases. We’ve also done a big update to our ChatOps internals, and we have early-access Ubuntu 18 + Python 3 packages (for test only!). Read on for full details.

At LogDNA, we’re all about speed. We need to ingest, parse, index, and archive several terabytes of data per second. To reach these speeds, we need to find and implement innovative solutions for optimizing all steps of our pipeline, especially when it comes to storing data.