Epsagon Documentation

Welcome to the Epsagon Documentation. You'll find comprehensive guides and documentation to help you start working with our product as quickly as possible. Let's jump right in!

Get Started

Setup Overview

Epsagon is designed to be simple to set up, with minimal instrumentation and automated tracing out-of-the-box. Epsagon is a SaaS platform, with no manual maintenance or longterm upkeep.

Getting started with Epsagon is a three-step process:

  1. Sign up for an account.
  2. Integrate your environment
  3. Trace your application

Epsagon specializes in Integrating all 3 pillars of observability under the same dashboard: metrics, traces, and logs.

📘

Setup recommendation

While some of the steps are optional, it is highly recommended to complete all of them in order to gain full observability into your stack and application.

Sign up

To signup just get into the signup page, and signup using email and password, or using the social SSO with Google or GitHub:

Once you're done, you'll be redirected to the onboarding wizard, the will instruct you to get started with integrating your first environment, and monitor your first application.

Integrating the environment

By integrating your environment, Epsagon automatically scans for resources, metrics, logs, issues and alerts, in order to provide you with predefined dashboards for monitoring and troubleshooting.

The following environments are supported:

  1. An AWS account.
  2. A Kubernetes cluster.
  3. An OpenWhisk namespace.

The integrations don't require any installations, setups, configurations, or maintenance. They don't incur any significant costs.

Integration mechanism

Tracing the application

Tracing helps you understand the performance of your application, and gain visibility into end-to-end calls and requests in your stack.

Using the automated tracing provided by the Epsagon libraries, you can easily see every call inside your application, capture exceptions, and understand the performance of your endpoints. Epsagon also captures the payloads from the calls (e.g. headers, body, params, and more) helping you troubleshoot issues much faster:

An example trace in Spring Boot, with Kafka, Load Balancer, and a DynamoDB

Updated 23 days ago


What's Next

Go ahead and integrate your environment or monitor your application!

Integrating Environments
Monitoring Applications

Setup Overview


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.