The cost of cybercrime is predicted to hit $10.5 trillion by 2025, according to the latest version of the Cisco/Cybersecurity Ventures "2022 Cybersecurity Almanac." The way that people work, the tools that they use, and the mindset they must adopt to protect the enterprise has to evolve to keep up with the threat landscape.
APIs have existed nearly as long as websites themselves. But because APIs are primarily consumed by programs instead of people, they tend to be less visible than applications or sites directly accessed by users. The result: APIs often receive far less attention from a site reliability engineering (SRE) and monitoring perspective than other parts of application environments.
With the rise of microservices and distributed systems, more and more data migrates through APIs. So, let’s look at the best ways to monitoring APIs using authentication.
An old colleague of mine once said to me, “It doesn’t matter how inefficiently something DOESN’T work.” This was a joke used to make a point, so it stuck with me. It also made me consider that it does matter how efficiently something DOES work. Sometimes, when we have tools like Cribl Stream making things like routing, reducing, and transforming data so easy, we can forget that there might be a more efficient way to do it.
From the moment Elastic announced plans to abandon a pure open source license for its Elasticsearch engine and Kibana dashboards in early 2021, there’s been a massive effort underway to create clear alternatives for the global community of active users. Logz.io has been an outspoken advocate and contributor to this work – fully embracing it as part of our product roadmap to best serve the needs of our customers, and preserve our long-term commitment to open source observability.
At first glance, availability monitoring may seem like one of the more mundane responsibilities of site reliability engineering (SRE) and IT operations teams. Determining whether an application is available may appear to be relatively straightforward, especially for teams that focus simply on monitoring certain transactions or services. This may have been true in the past.
Git integration has always been at the foundation of Stream. In the fall 2021 release of Cribl Stream (both on-prem software and Cloud), our Enterprise users have a received set of APIs to separate the development and deployment of Stream. Stream GitOps connects with your favorite git based versioning platforms and leverages their PR, approve/reject, and CI/CD workflows to push production-ready changes from a development branch into a main branch or release.
Synthetic monitoring tools have long formed a core part of application performance management and monitoring toolsets. Yet no matter how familiar you are with synthetic monitoring, there is likely room to get more out of it than you currently are. Indeed, the default approach to synthetic monitoring tends to involve using it reactively: problems occur in production, and your team uses synthetic monitoring to help understand and remediate them.
It’s been an exciting few days at Cribl. A week ago, we announced our $150 Million Series D funding round led by Tiger Global, with participation from existing investors IVP, CRV, Redpoint Ventures, Sequoia Capital, and Greylock! We also announced an exciting new product: Cribl Search! We’ve been blown away by the excitement from our customers thus far.
