OpenStack is, by definition, a flexible and agile platform, which enables its users the selection of a diverse set of X-aaS capabilities, easy and accessible documentation, a vibrant community with a strong base of technically-sufficient individuals and so much more.
But did you know….?
Having said that, It's an industry-given that Openstack has it's monitoring pains, we've already mentioned them in our previous blog post, but here's a quick TL;DR: Frequent updates, insufficient support for containers, scaling issues, complex installations, unintuitive dashboards, poor documentation, and painful integrations with on-premise infrastructure.It comes as no surprise that OpenStack itself has already addressed a few of these issues, and mentions many (and more!) of the above in its Wiki, went ahead and offers suggestions to a few of these issues. OpenStack went a step ahead and mentioned in its OpenStack’s 9th User Survey a few of these known faults, such as the fact that Error handling and messages should be improved, a problem that compels the end user to trawl twice and double the effort due to its disparate nature.
In this survey, amongst other pains, some users mentioned that "stability is my main issue with OpenStack", especially in a Production-ready environment. Just another issue on its own.
Curious to hear more from developers, we went ahead and have recently conducted a survey, which reveals the real thoughts of developers and main pain of actual people using Openstack on daily basis. We asked the following question:
"What are the main problems you face today in your OpenStack environment?"
The answers we received did not blow our minds, to be quite honest, but helped shedding some more light on existing pains and what are the main issues that end users have with OpenStack. The results are as follows:
40% mentioned that they usually can't determine the actual root cause of issues, preventing them from taking considerable measures to solve the issue to its core. This methodology prevents organizations from acting and limits them to symptomatic threat treatment, meaning the issues can be recurrent.
Over 32% claimed they are too reactive, and hear about most of the issues from their users post mortem, after the fact. This is naturally an issue which can severely affect customer experience and down the line effect overall revenues.
18% said they have silos, and that no one in their IT operations actually has a clear understating, and ever more so- an overview of their OpenStack environment. It's only natural that large organizations are departmentalized, however this approach can cause latency in internal problem solving and end up in elevated MTTRs.
And finally, 10% admitted that resolving issues in their OpenStack environment takes too long. In the case of disparate tools across the whole stack, a very valuable resource, man-hours is being directed to maintenance and lots of manual work, which frequently ends up in a dead end due to low capacity.
To sum up, OpenStack monitoring, based on the survey we conducted as well as the industry discourse, has its unique issues. Since have been frequently been asked about these issues, we decided to host a webinar on the matters at stake, dedicated to OpenStack pains and how to (really) overcome them.
Join our webinar, hosted by Loom's VP prodcut, Dror Mann, this Thursday, September 14th to learn more.
Looking forward to seeing you there!
Loom Systems delivers an AIOps-powered log analytics solution, Sophie,
to predict and prevent problems in the digital business. Loom collects logs and metrics from the entire IT stack, continually monitors them, and gives a heads-up when something is likely to deviate from the norm. When it does, Loom sends out an alert and
recommended resolution so DevOps and IT managers can proactively attend to the issue before anything goes down.
Get Started with AIOps Today!