> For the complete documentation index, see [llms.txt](https://revdebug.gitbook.io/revdebug/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revdebug.gitbook.io/revdebug/master.md).

# Introduction

RevDeBug is a platform for monitoring distributed systems that provides automatic code instrumentation and agent-less monitoring. With end-to-end tracing and effortless observability for all of your cloud-native or on-premises applications.

## RevDeBug Architecture

![RevDeBug Top-Level Architecture](/files/Ucfq9Zq4YHlcshs01mFT)

RevDeBug consists of two elements:

* RevDeBug Server used to gather and record the metrics and execution/error recordings - deployed within your own cloud tenant or on-premises.
* RevDeBug application dependencies - libraries and packages used to automatically integrate RevDeBug with the applications.

## Quickstart

To start using RevDeBug you need to complete those two easy steps:&#x20;

1. [Install RevDeBug Server](/revdebug/installing-revdebug-server.md#setting-up-revdebug-server-instance)
2. Instrument your applications
   1. [C#](/revdebug/supported-langauges/c.md)
   2. [Java](/revdebug/supported-langauges/java.md)
   3. [JavaScript and TypeScript](/revdebug/supported-langauges/javascript.md)
   4. [Python](/revdebug/supported-langauges/python.md)
3. [Repository Configuration](/revdebug/repository-configuration.md)

{% hint style="info" %}
**We will be grateful for any comments on the features as well as suggestions for product development.**

**Reach out to us at** [**contact@revdebug.com**](mailto:contact@revdebug.com)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://revdebug.gitbook.io/revdebug/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
