First, let me introduce myself: My name is Christina Wong and I joined Thundra in May 2018 as VP of Marketing. My background includes roles in mechanical engineering, sales, product marketing, and partnerships across a variety of different sized organizations (from startup to large companies) and in several different industries (automotive, defense, software). I love working in the space where business and complex technical topics intersect and I am especially fascinated by new software challenges and adoption of new application paradigms of all sorts. This includes cloud, microservices, containers, devops, and, now, serverless. In my spare time, I am a mechanic and race car driver on a team called The Cosmonaughts.
Greetings, everyone! I’m happy to announce our first official release — the Thundra Serverless Observability for Splunk App. Available immediately, this Splunk app adds AWS Lambda observability and monitoring to your Splunk Enterprise deployments. This allows you to include information about the health of your serverless environment alongside your other enterprise systems.
For those of you unfamiliar with Splunk, organizations use Splunk to analyze, monitor, and visualize machine-generated data from their IT infrastructure and business. With data from servers, webpages, devices, applications, and other sources combined into a single view, an organization can understand how their business systems are running separately, and together, in real-time.
As we’ve mentioned in our blog, “The state of serverless observability — why we built Thundra”, serverless applications are still new and lacking in the tools, best practices, and ecosystem maturity required to become truly “enterprise-friendly.” One challenge is most organizations are unable to really understand (and therefore debug and optimize) how their serverless environments are performing. Also, most enterprises need to be able to analyze this information alongside their other enterprise IT system data.
Now, with the Thundra’s new Splunk App, you can solve both of these problems in a single solution. Let’s take a look at the various components of this offering and how you can accomplish this.
Thundra’s Splunk solution consists of three components
The Thundra Lambda Agent: This AWS Lamdba function monitors and collects your Lambda environment data
The Thundra Integration for Splunk CloudFormation stack: This stack consists of:
- The Thundra Receiver App that collects, transforms, and aggregates data from the Thundra Lambda agent.
- The Splunk universal forwarder that sends that data to your Splunk instance.
- A data volume that temporarily stores the files and data collected from the Thundra agent. This data volume cleanses the Thundra data hourly.
The Thundra Serverless Observability for Splunk App: This is Thundra’s Splunk App that allows you to visualize your serverless data in your Spunk deployment.
Quick overview of Thundra’s Splunk visualizations
Let’s take a look at some of the things you can learn using Thundra’s Splunk visualizations. For more in depth information, please check out our Splunk App documentation.
The Overview page lets you see an at-a-glance, top-down view of your serverless environment over a specified period of time. Quickly determine which functions are most invoked, which are throwing the most errors, and which are cold when starting up. (Read more on the Overview page here.)
Our dashboards includes several summary pages useful for understanding your serverless environment from various perspective. For example, the Functions page will give you a summary of the functions which are invoked most in your system. (Read more on the Functions page here.)
Alternatively, you can also explore everything there is to know about a *single* function via the Function Details page.
You can even perform anything from basic to advanced analysis, including invocation counts, memory and CPU usage, and requests to external resources. (Read more on the Functions Details page here.)
If you are interested in how your functions are interacting with a certain type of external resource, you can use the External Resources pages. These dashboards show you how all your functions are interacting with, say, HTTP endpoints. Or, you can choose to view a specific URL to see which functions are requesting interactions with that particular URL. (Read more on the External Resources page here.)
And there’s lots more! Want an official tour of our new offering? Check out our Splunk integration page for a deeper overview plus videos for a walk though.
Thundra offers rich observability and monitoring of serverless environments and we hope this integration with Splunk is particularly beneficial for those who are interested in analyzing their serverless data alongside the rest of their data. We are rapidly adding new features, functionality, and integrations. Keep checking back here for the latest updates and follow us on Twitter and LinkedIn!