How did this affect your decision to include B2 Cloud Storage as one of these storage destinations and how is it serving Cloudflare and its customers’ needs?Ī: Cloudflare values open ecosystems in technology-we believe that customers should not have to be locked in to any single provider. In the spirit of building a better internet, we’ve helped a number of companies reduce data transfer fees via the Bandwidth Alliance. Q: This isn’t the first time Backblaze and Cloudflare have worked together. ![]() With the increased adoption of S3-compatible storage, we thought it would be a great spot for us to create our own endpoint to be able to serve more platforms. Q: What sparked the push to support more S3-compatible storage destinations for Logpush data?Ī: S3-compatible storage is becoming an industry standard for cloud storage. Platform-wide analytics are very powerful in giving customers a holistic view of their entire system. Customers can use platform-wide analytics to understand the activity of IP addresses from both within the Cloudflare network and other applications in their infrastructure. For example, a typical L7 DDoS attack originates from a handful of IP addresses. This combined data is very useful not only for day-to-day monitoring, but also when conducting network forensics after an attack. From there, customers can combine Cloudflare logs with those of other tooling in their infrastructure, such as a SIEM or marketing tracking tools. They simply set up a job using the Logpush API or with the click of a few buttons in the Cloudflare dashboard. Q: What makes it compelling to Cloudflare customers? Are there specific use cases you can touch on? Any light you can shed on how a beta tester used it when you first announced it?Ī: Logpush makes it very easy for customers to export data. Rather than the need for customers to configure and maintain a system that makes repeated API calls for the data, with Logpush, customers configure where they would like to send their logs and we push them there directly on their behalf. We decided to create Logpush to solve both these problems. We also frequently heard that customers want their logs in real time or as near as possible. Increasingly, we were hearing repeated use cases where customers would want to integrate with common log storage and analytics products. Q: Cloudflare already offers Logpull, what’s the difference between that and Logpush?Ī: Logpull requires customers to make calls to our Logpull API and then set up a storage platform and/or analytics tools to view the logs. Logpush makes these logs available for Enterprise customers to get visibility into their traffic, quickly and at scale. As part of providing these services for customers, we generate logs for every request in our network. We analyze the traffic going through our network to perform actions such as routing traffic to the nearest data center, protecting against attacks, and blocking malicious bots. ![]() How does it fit into the Cloudflare ecosystem and what problems is it solving for?Ī: Cloudflare provides security, performance, and reliability services to customers behind our network. ![]() Q: Tell us more about the origins of Logpush. When we heard about their new Logpush tool, I reached out to Tanushree Sharma, the product manager on this project, to learn more about why they built it, how it works with Backblaze B2 Cloud Storage, and what comes next. As big believers in open ecosystems, interoperability, and just making life easier for developers, Backblaze and Cloudflare share a lot-which means we’re always excited to dig into new functionality they’re providing for devs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |