Operations | Monitoring | ITSM | DevOps | Cloud

To get some serious work done, we usually need to prepare for it. “Baby steps first,” they say. In our niche, these “baby steps” would be countless small jobs that need to be done before we can start with our main project. Proper preparation(try saying this 5 times fast) is the key to success, but after we’ve achieved our primary goal, there will always be something to do to keep it steady and flowing.

Azure Network Security Groups (NSG) are used to filter network traffic to and from resources in an Azure Virtual Network. If you’re coming from AWS-land, NSG’s combine Security Groups and NACL’s. Splunking NSG flow log data will give you access to detailed telemetry and analytics around network activity to & from your NSG's. If that doesn’t sound appealing to you yet, here are some of the many things you could Splunk with your network traffic logs from Azure.

xMatters provides flexible, smart tools for incident response and management. With configurable workflows that bring together data from sources like Github, Jenkins, and Zendesk, you can automate crucial tasks and send enriched notifications to streamline team communications.

Sometimes you need tools to manage your tools. If Zapier is your tool of choice, you can now add your Uptrends alerting as one of those tools ready for automation with Zapier.

Health and performance issues are easier to understand—and to troubleshoot—when you can use tags to aggregate your data across many overlapping scopes. But while some scopes come directly from your infrastructure, others are constantly evolving to reflect the needs of your product or organization. You can only track your data effectively if you can define—and redefine—your scopes on the fly.

If you’ve ever used Ruby on Rails, you’ve probably come across the concept of concerns. Whenever you jumpstart a new Rails project, you get a directory app/controllers/concerns and app/models/concerns. But what are concerns? And why do people from the Rails community sometimes talk badly about them?

For many organizations, knowledge management is often considered a technology problem. This is why when they implement knowledge management, the execution is often rendered unsuccessful because the processes and the kind of articles that are created are too complicated for people to use. ITIL knowledge management is defined as the process of capturing, processing, storing, and sharing knowledge across the enterprise.