2020 is finally over and all of us are hopeful of a return to a sense of normalcy in 2021. At LogicMonitor, we came back re-energized from a healthy year-end break and are putting the finishing touches on our product roadmap for this year. This is a great opportunity to look back on what we accomplished in 2020 despite all of the challenges we faced.
So you’ve now finally finished putting all the pieces together – transitioned to Azure, deployed resources, deployed applications, got familiar with Azure Monitor and set up all the monitoring. You’re now collecting all the monitoring, application performance and security data for your Azure resources in Log Analytics workspaces, ready for analysis. (Head over to our Azure Monitor Learning Path if you're still figuring out how to do all that.) But is only the collection enough?
We’ve been doing some Ruby on Rails development lately, in preparation for PagerTree 4, and we wanted to put together a Ruby on Rails Cheat sheet. This is a quick reference guide to common ruby on rails commands and usage.
No matter your business, keeping customer data secure is critical toward keeping your customer’s trust. With the rise in data breaches (and subsequent security certifications), we don’t have to tell you why you should scrutinize every cloud service that you consider — including us. To that end, we believe in being explicit with our compliance. And that includes how we pursue independent certifications like ISO, HIPAA, and now, SOC 2 Type II.
Using the cloud reduces on-premises infrastructure costs and related maintenance. Instead of deploying more servers, storage, and networking components to your own datacenter, you are now deploying these as cloud resources. Using the cloud is supposed to reduce infrastructure and maintenance costs. However, deploying cloud resources also risks over-commissioning, under-usage, and keeping resources running that are not always needed or, even worse, no longer in use.
An IT project can introduce a variety of challenges during implementation. The IT team handling the project should constantly improvise and embrace mid-project adjustments to make sure everything is in place. This is especially true when dealing with a company-wide change that might come with varying levels of complexity, risk, and impact. Project management in ITSM ensures seamless implementation of complex IT projects within the stipulated deadline.
