Observability and performance testing — the two disciplines at the heart of performance engineering for modern distributed systems. The list covers production-grade tools (metrics, tracing, profiling, load testing, chaos engineering, CI/CD integration) alongside practical guidance on when and why to use them.
I created this list because I've spent years working on performance for large-scale systems and kept noticing the same gap: observability tools and performance testing tools are almost always discussed separately, but in practice they're deeply interconnected. You can't interpret load test results without good observability, and you can't validate observability setups without realistic load. This list bridges that gap.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/3952
**Author:** [@be-next](https://github.com/be-next)
**Created:** 2/18/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `add-performance-engineering`
---
### 📝 Commits (1)
- [`25913d2`](https://github.com/sindresorhus/awesome/commit/25913d260ab62f852efa6e4a6a26279c16b43657) Add Performance Engineering
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
**What is this list about?**
Observability and performance testing — the two disciplines at the heart of performance engineering for modern distributed systems. The list covers production-grade tools (metrics, tracing, profiling, load testing, chaos engineering, CI/CD integration) alongside practical guidance on when and why to use them.
I created this list because I've spent years working on performance for large-scale systems and kept noticing the same gap: observability tools and performance testing tools are almost always discussed separately, but in practice they're deeply interconnected. You can't interpret load test results without good observability, and you can't validate observability setups without realistic load. This list bridges that gap.
---
### By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.
- [x] I have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- [x] This pull request has a title in the format `Add Name of List`.
- [x] The entry in the list has an appropriate description with a capital letter and ends with a period.
- [x] The entry is added at the bottom of the appropriate category.
- [x] The list I'm submitting complies with these requirements:
- [x] Has been around for at least 30 days (first commit: January 13, 2026).
- [x] It's the result of hard work and the best I could possibly produce.
- [x] It is a non-generated Markdown file in a GitHub repo.
- [x] The repo has `awesome-list` & `awesome` as [GitHub topics](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics).
- [x] Not a duplicate.
- [x] Only includes awesome stuff (curated, not exhaustive).
- [x] Includes a project logo/image.
- [x] Entries have descriptions.
- [x] Has the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge).
- [x] Has a Table of Contents section named `Contents`.
- [x] Has an appropriate license (CC0).
- [x] Has [contribution guidelines](https://github.com/be-next/awesome-performance-engineering/blob/main/CONTRIBUTING.md).
- [x] Consistent formatting and no hard-wrapping.
- [x] No CI badge in the readme.
- [x] Default branch is `main`.
- [x] Passes [`awesome-lint`](https://github.com/sindresorhus/awesome-lint).
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/3952
Author: @be-next
Created: 2/18/2026
Status: 🔄 Open
Base:
main← Head:add-performance-engineering📝 Commits (1)
25913d2Add Performance Engineering📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
What is this list about?
Observability and performance testing — the two disciplines at the heart of performance engineering for modern distributed systems. The list covers production-grade tools (metrics, tracing, profiling, load testing, chaos engineering, CI/CD integration) alongside practical guidance on when and why to use them.
I created this list because I've spent years working on performance for large-scale systems and kept noticing the same gap: observability tools and performance testing tools are almost always discussed separately, but in practice they're deeply interconnected. You can't interpret load test results without good observability, and you can't validate observability setups without realistic load. This list bridges that gap.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.
Add Name of List.awesome-list&awesomeas GitHub topics.Contents.main.awesome-lint.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.