Operations | Monitoring | ITSM | DevOps | Cloud

Choosing a software solution means checking the right boxes, and being “cloud native” has bubbled to the top of most lists. But cloud native is a box built of boxes of its own. For a CI/CD solution like JFrog Pipelines, cloud native starts by being “born in the cloud” to natively execute in, build for, test in, and deploy to cloud computing environments. But what boxes does a CI/CD solution really need to tick to complete that larger cloud native box?

It’s been almost a year since the world changed overnight and industries across the world quickly adapted to living, working, and learning fully virtually. While the world seemed to stop in an instant, many businesses saw an increase in demand and new challenges. PagerDuty was no different.

This is a follow up to a blog series where we explore DIY cloud cost management, monitoring, and optimization tools. In the first, we investigated how Lyft, Netflix, Segment, Expedia, and Slack built theirs. Check it out here. “Build versus buy” is the eternal question for every engineering and DevOps team setting out to solve a technical problem. In the cloud cost monitoring and optimization world, both options can take on many forms.

In this article we will focus on our on-premise platform, or cloud monitoring after having installed Pandora FMS console in Microsoft Azure. The installation will be made with an automated script that installs the Community version and with a second script, it allows to update Pandora FMS to its Enterprise edition (Corporative), leaving a 30-day test version (Trial).

This is my first week here as the first dedicated SRE for Honeycomb, and in a welcoming gesture, I was asked if I wanted to write a blog post about my first impressions and what made me decide to join the team. I’ve got a ton of personal reasons for joining Honeycomb that may not be worth being all public about, but after thinking for a while, I realized that many of the things I personally found interesting could point towards attitudes that result in better software elsewhere.

The importance of effective data analytics within an organization is widely accepted by business leaders at this point. With use cases for data analysis spanning every department—from IT management, financial planning, marketing analytics, and so on—the right data analytics tools can have a significant impact on a company’s profitability and growth.

In the 1995 movie Apollo 13, one man with a buzz cut told another man with a buzz cut (who then told several other men with buzz cuts) that “failure is not an option.” And thankfully for that extraordinarily dramatic event, it was true. It would be nice if the same commandment held for websites. However, even an infinity of buzz cuts cannot change the fact that, alas, sometimes websites fail.

Maybe you have used the previous blog post about generating smarter episodes in ITSI using graph analytics and want to know what else you can apply ML to. Maybe you’re still swamped in alerts even after using the awesome content pack for monitoring and alerting. Maybe your boss has told you to go read up on AIOps…. Whatever the reason for finding yourself here this blog is intended to help you identify the “unknown unknowns” in your alert storms.

Like champagne and party hats, Splunk and Microsoft just go together. Here at Splunk, one of our New Year’s resolutions is to continue to empower our customers with data — in this case, Microsoft data. From cloud, to security, to troubleshooting, we’re back with the latest round of new integrations designed to help you do more with Splunk and Microsoft.

Network address translation (NAT) is very simple in concept. As packets pass through some network device—typically a firewall, router, or load balancer—either the source or destination IP address is changed. Then packets returning in the other direction are translated back to the original addresses. In some cases both are changed at once, which is called “twice NAT” in some documentation.