Operations | Monitoring | ITSM | DevOps | Cloud

As you build more complicated Splunk apps, you might wonder, “What is the best way to make the features in my app more usable?” If you’re adding new SPL commands or creating ways to input new data sources, the answer is straightforward. But imagine you’re trying to address one of the following scenarios: For cases like these, consider extending the Splunk REST API with custom endpoints.

Focusing on these five essential workflows for secure DevOps will help you get started implementing monitoring, security, and compliance for containers and Kubernetes. You might be starting to adopt DevOps and find that it dramatically simplifies deploying applications in containers and Kubernetes. However, you probably also found that it adds a new set of complexities for managing, securing, and troubleshooting applications.

Evan Niedojadlo is an SRE at Peddle based in Austin, TX. He is currently on a small team and works on the SRE, Ops, and Security area of the organization. In his free time, he enjoys building communities, reading, music, helping others learn, and being outside.

At the recent PromCon Online, I gave a review of developments in the space of the Prometheus storage engine, TSDB. In this blog post I am going to recap a bit of the talk and add more insights into what these developments will enable us to do in the future. While the talk contained some of the near-future features, I will be diving even further ahead. You can watch the talk here.

At Taloflow, we’re proud to introduce to you our newest partner, Xosphere. The Xosphere™ Instance Orchestrator™ intelligently manages AWS Spot instances to give your applications 100% reliability at a fraction of the EC2 cost. Customers of Taloflow can use Xosphere in conjunction with Taloflow’s services to seamlessly identify candidates for Spot Management and monitor improvements in EC2 efficiency.

Sysadmin Day 2020 is right around the corner and we’d like to show our appreciation for all the sysadmins out there who keep IT humming along and come to the rescue to resolve critical issues day in and day out. This year, we’re celebrating all week long by hosting an IT Heroes and Homelabs contest. Join the celebration by retweeting our post with the hashtag #SysadminDay #NetdataWin, and we’ll enter you in a drawing to win some Netdata swag!

With open source in our roots, we’re always excited about integrations with tools like OpenVAS, a popular open source vulnerability scanner that Greenbone Networks has maintained since 2009. If you’re not currently using OpenVAS, you can find the project here. OpenVAS contains more than 50,000 vulnerability tests with a community constantly updating its feed to adapt to the ever-evolving security landscape.

It’s been more than a year-and-a-half since we started using Cypress for our automated functional testing, and it has been well worth the investment. Cypress has now become an essential part of our process to automate regression testing, which helps us ship new releases faster, with increased quality.

While the concept of zero-trust security has many IT organizations thinking in terms of identity, access, and cloud services, zero trust must run on a solid foundation. We should start by talking about the goals of zero-trust security. Zero trust involves creating an environment where each access request is first scrutinized to determine whether it should be allowed.

Feature branch workflows are used to isolate work done on a specific feature in a dedicated branch. This allows all development to be kept away from the team’s common codebase until completion. Essentially keeping the master safe from any risk until it is ready to be merged.