The Intigua Blog
In May 2017, the WannaCry vulnerability caught the IT world by surprise. In the blink of an eye, an estimated 200,000 computers worldwide were infected with crippling ransomware. The attack exploited a vulnerability in the antiquated version 1 of Server Message Block (SMB), a critical remote service and file sharing protocol for Windows servers.
We’ve recently started to work with a new cloud services provider - Virtustream, an important and growing member of the Dell Technologies family. Virtustream is a large business, having been acquired by Dell for over $2B. At Intigua we haven’t reached a 10-digit valuation (yet...), but as we started to work with the Virtustream team, we were thrilled to find out how much our two companies have in common. Most importantly, both our companies share a common view of today’s enterprise IT challenges.
Splunk and Sumo Logic both compete for a similar target market within the log management and analytics space. On the surface, their offerings primarily differ in deployment model—Splunk offers an on-premises solution while Sumo Logic’s product is cloud-based. Yet, each solution brings its own value propositions and considerations, and each impacts customers differently. The following is a detailed comparison between Splunk and Sumo Logic
The Intigua Packager lets you package any tool agent for use with Intigua. However, we also have an extensive library of tool agents we have already pre-packaged for use with Intigua.
We constantly add new tools and versions to this library. Here are some recent additions:
In this case study, we describe how publicly traded PTC's Cloud Services division accelerated DevOps by automating tool management and improving agent uptime with the Intigua Agent Manager.
You now have another option on where you can run the Intigua Agent Manager -- in the Azure cloud. Until now you could either download Intigua and run it on-premise or run it on AWS through the AWS Marketplace. Now you can do the same with the Azure Marketplace -- and pay for Intigua on a per hour/per server basis.
Puppet, Chef, Ansible and SaltStack present different paths to achieve a common goal of managing large-scale server infrastructure efficiently, with minimal input from developers and sysadmins. All four configuration management tools are designed to reduce the complexity of configuring distributed infrastructure resources, enabling speed, and ensuring reliability and compliance. This article explores the mechanism, value propositions and concerns pertaining to each configuration management solution.
In an ideal world, environments would all be identical. All servers would run the same OS, have the same networking configuration, store their data in the same way and so on. In that situation, there would be perfect equivalence between environments.
But this is not a perfect world (it’s also not as boring as one in which everything looks the same), and perfect environment equivalence is never going to happen. Even when ITOps teams try hard to maintain homogeneity across their infrastructure, environment variability always creeps in in one way or another.
But that doesn’t mean ITOps is helpless in the face of this environment variability. There are solutions. In this post, I take a look at this issue, then explain how the challenge can be overcome using container-based software agents in order to optimize the management of servers across variable environments.
One of the most important IT has is to enforce standardization and governance across all managed infrastructure. This seemingly simple task can prove very difficult as IT teams manage heterogeneous IT workloads, or embrace more bimodal IT models in which the traditional on-prem/data center IT environment evolves into more cloud resources and different demands from users. As a result, ITOps teams need to reinvent the way they deploy, manage, and automate policies across their servers.
For savvy DevOps folks, this should raise alarm bells: What is deployed where? Is it on-prem or in a public cloud? In the latter case, in which region does it exist, and under whose policy? Answering these questions requires visibility into the services running on-prem as well as on private and public cloud servers.
Gaining visibility has traditionally been complex and costly, hence the dreaded “microservice premium.” But assuring visibility is critical for teams scaling to cloud infrastructure or microservice architectures.