> For the complete documentation index, see [llms.txt](https://docs.ddosify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ddosify.com/ddosify/getting-started.md).

# Getting Started

<figure><img src="/files/0qNd8QpNV0wbfbXHxzYy" alt=""><figcaption><p>Ddosify detects high latency service calls on your K8s cluster</p></figcaption></figure>

### Ddosify Features

:white\_check\_mark: **Kubernetes Monitoring**

&#x20;    Effortlessly visualize Kubernetes clusters as Service Map. Inspect HTTP latencies, find idle services, and get actionable insights.

:white\_check\_mark: **No-code Performance Testing,**

&#x20;   You can create complex and realistic user flows on Ddosify's No-code UI. Here are the list of key concepts on Ddosify's No-code UI.

* [Parametrization](/ddosify/performance-testing/parametrization.md)
* [Test Data Import](/ddosify/performance-testing/test-data-import.md)
* [Environment Variables](/ddosify/performance-testing/environment-variables.md)
* [Correlation](/ddosify/performance-testing/correlation.md)
* [Assertion](/ddosify/performance-testing/assertion.md)
* [Debugging](/ddosify/performance-testing/debugging.md)
* [Postman Import](/ddosify/performance-testing/postman-import.md)

:white\_check\_mark: **Detailed Reporting**

&#x20;     Insightful reports and charts to improve your observations. Analyze the failed requests on UI.

### **How to start**

➡️ Follow the [Kubernetes Monitoring](/ddosify/kubernetes-monitoring.md) section to learn about effortless Kubernetes Monitoring using eBPF.

➡️ To understand how to set up no-code Performance/Load Testing using Ddosify Cloud or Ddosify Self-hosted, check [Performance Testing](/ddosify/performance-testing.md).


---

# 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://docs.ddosify.com/ddosify/getting-started.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.