WHY SERVERLESS OBSERVABILITY?

WHAT IS “SERVERLESS”?

Focus only on creating amazing code

When you employ a “serverless” application approach you are aiming to greatly reduce your operational burden and un-utilized overhead to focus solely on activities that drive and create business value, such as writing new applications and features. With this approach, your developers write code and sends it into the vendor’s environment, who takes on the responsibility of spinning up all the hardware, software, and networking required to run that code. You only pay for the resources used while the code is being executed.  

With this approach, you no longer need to worry about:

  • High availability - ensuring the application works when you want it to
  • Scalability - ensuring the application continues to perform even as it receives heavy amounts of traffic or loading
  • Fault tolerance - ensuring the application continues to perform even if portions of the software, hardware, or network fail
  • Paying for or maintaining underutilized resources whose only purpose is to be available in case the application needs it to maintain acceptable performance
serverless-logo-6B587FD8CB-seeklogo.com

WHY OBSERVABILITY AND MONITORING?

MONITORING: Watch known system variables to understand overall system health and identify when something is going wrong
OBSERVABILITY: Observe and monitor system behavior for insights on how to improve and to spot unanticipated problems or inefficiencies.

TRACES

Gain end-to-end visibility through entire request chains. Including,

  • Identifying performance bottlenecks.
  • Detecting components causing errors.
  • Debugging domain-level bugs.
METRICS

Track measured or calculated time-series information from applications, modules, layers, and domains, including:

  • CPU and memory usage.
  • Frequency, volume, and timing of errors. 
  • Duration of function, requests, and responses.
LOGS

Read through immutable and verbose representation of discrete events for support in:

  • Debugging.
  • Auditing.
  • Analyzing system behavior.

SPOT ISSUES QUICKLY WITH THUNDRA


  • Identify your long running functions.
  • Understand which functions are being called at the highest and lowest frequencies.
  • See which functions are experiencing cold starts.
  • Discover inefficiencies throughout your environment.
  • Track which functions are interacting with which external services


thu-why-thundra@2x

Curious to try it out? Play with our live monitoring environment. No sign up required!
TRY IT NOW