Microsoft recently reported two widespread cryptomining attacks targeting Kubeflow, a popular cloud-native platform for machine learning (ML) workloads on Kubernetes. Attackers targeted Kubeflow installations using either the Kubeflow central dashboard interface or Kubeflow Pipelines interface for scheduling crypto-mining workloads.
Regardless of how technically sound the engineering of an app is, bugs, errors, and crashes can happen. So when they do, you must recover from it by doing a deep analysis of the technical aspects and the impact on the overall customer experience. If your crypto-exchange or banking app is not getting the right insights you need from the crashes, your churn rate and your customers will definitely let you know sooner than you think.
Over time technologies evolved and now things that seemed to be not possible several years ago become the reality. Now you can order food, services, and basically anything you need online, and pay for it without leaving home. No surprise here, that cash payments are becoming a relic of the past. Along with wireless payments like Google or Apple pay (that still require assigning a banking account or card i.e. physical currency), the cryptocurrencies like Bitcoin are getting widely used.
Crypto trading and exchange apps have surged in recent years as a direct consequence of the exponential growth in the number and market capitalization of cryptocurrencies. With ever-growing press coverage and heightened visibility, the crypto ecosystem gets more and more crowded every second. This constant influx of players has clearly been beneficial, as the assets traded continue to grow.
The way we ‘data’ is about to change, and Splunk’s Connect for Ethereum (aka EthLogger) is helping organizations to adapt. Splunk Connect for Ethereum enables organizations of all sizes to investigate, monitor, analyze and act upon their rapidly growing blockchain data sets across multiple chains.
All the work presented in this blog post is open source and available as part of our Splunk Connect for Ethereum repository examples, including the instrumentation of Besu as a Docker container, the configuration of Splunk, and two applications showing how to monitor Besu syncing to the chain.
A couple of years ago, I wrote about why you don’t need a blockchain. Blockchain is one long transaction log that always gets written to and is never backed up. It’s a ledger, more or less, with some math. And while distributed ledgers can be useful for some scenarios, I’m here today to say you still don’t need a blockchain. What turns a distributed ledger into a blockchain is cryptography for creating a digital signature to reduce the risk of data tampering.
ETHDenver connects developers, technologists, cypher punks, coders, crypto-economists, designers and makers to build on Ethereum, making it the perfect place to debut Splunk Connect for Ethereum. The use cases we saw added observability to blockchains like Ethereum mainnet and sidechains in real time. As the event went on, use cases and requests continued to pop up (which you'll see below); the app was used to index not just ethereum mainnet, but also sidechains such as xDai and OST Mosaic.
