When you start a company – or a third company as is the case for Lee and me – you start with a problem statement, a product you believe in, and a lot of hope. This means when growth goes as planned or exceeds expectations, you shouldn’t be surprised. This is what is supposed to happen. Great Product + Market Opportunity + Great Team = Successful Business. Intellectually, I know all this, but it is still exciting to see it come to fruition.

From online banking, insuring cars, and shopping, we are almost totally reliant upon the internet to complete daily tasks and make our lives easier. However, as technological advancements give us greater convenience, increase productivity, and provide greater access to whole new swathes of entertainment, consumers and businesses alike leave themselves at risk of cyberattacks against which robust defenses must be in place.

In times where it is possible to instantly access information, the website is the main point of communication with the market for every company. The website is often the place where the crucial first impression is built. It generates leads, sells, provides customer service, gets in touch with the media, recruits etc. It is the company’s website that the traffic from advertising campaigns gets directed to—and not only from the online ones.

So you have been adding more and more logs to your Graylog instance, gathering up your server, network, application logs and throwing in anything else you can think of. This is exactly what Graylog is designed for, to collect all the logs and have them ready for you to search through in one place. Unfortunately, during your administration of Graylog you go the System -> Overview screen and see the big bad red box, saying you are having indexing failures.

Continuous integration and continuous deployment (CI/CD) has enabled teams to build and deploy software at a much faster pace. DevOps teams can build, test, and deploy changes to production in a matter of minutes, allowing for extremely rapid release cycles. However, a CI/CD pipeline has a lot of moving parts and steps where problems to occur. In order to ensure a successful deployment, it’s important to monitor each step in this process.

Every day that I commute home, I check Google Maps for the next Trimet bus arrival at the usual stop. There’s nothing wrong with this ritual but it always distracts or leaves me stalled for a few empty minutes. Ever the proponent of laziness automation, I decided to build a stack that will do this for me by texting incoming arrival times for my bus home.

Ben Kehoe wrote a post about AWS API Gateway to Lambda integration: How you should — and should not — use API Gateway proxy integration with Lambda. In his post, Ben gave a few reasons why he believes using API Gateway Proxy Integration is an anti-pattern. Ben does a great job summarizing how the integration works. He writes: The pattern that I am recommending against is the “API Gateway proxy integration” as shown in the API Gateway documentation here.

DevOps, security, and SOC teams find themselves constantly facing new cyber threats, ever-evolving attackers, and innovative attack vectors. Their challenges range from protecting employees’ mobile devices to preventing malicious parties from accessing an organization’s financial data or customers’ personal information.

Launched at KubeCon North America last December, Loki is a Prometheus-inspired service that optimizes storage, search, and aggregation while making logs easy to explore natively in Grafana. Loki is designed to work easily both as microservices and as monoliths, and correlates logs and metrics to save users money. Less than a year later, Loki has almost 6,500 stars on GitHub and is now quickly approaching GA.