Automatic Analysis Reports in OpenResty XRay
- The Past
- The Present
- The Future
- The Past
- The Present
- The Future
Featured Articles
OpenResty XRay reduce your CPU usage up to
90%
OpenResty XRay reduce your CPU usage up to 90%
Latest Articles
How a Single "0" Took Down Bilibili — Every Server at 100% CPU, and Reboots Didn't Help
- The Platform Behind Hundreds of Millions of Streams
- The July 2021 Bilibili Outage: When Rebooting Doesn’t Help
- Finding the Root Cause with CPU Flame Graphs
- One Type Mismatch, Entire System Down
- The Platform Behind Hundreds of Millions of Streams
- The July 2021 Bilibili Outage: When Rebooting Doesn’t Help
- Finding the Root Cause with CPU Flame Graphs
- One Type Mismatch, Entire System Down
Nginx Regex Performance: Find Slow Patterns with Dynamic Tracing
- Prerequisites and Setup
- Locate Slow Regex with CPU Flame Graphs
- Performance After Regex Optimization
- Limit PCRE Backtracking with lua_regex_match_limit
- Non-Backtracking Engines: RE2 and OpenResty Regex
- Lua Built-in Patterns as a Regex Alternative
- Trace Regex Performance in Docker and Kubernetes
- How the Dynamic-Tracing Tools Work
- Tool Overhead: Zero Impact When Not Sampling
- FAQ: Nginx Regex Performance
- Prerequisites and Setup
- Locate Slow Regex with CPU Flame Graphs
- Performance After Regex Optimization
- Limit PCRE Backtracking with lua_regex_match_limit
- Non-Backtracking Engines: RE2 and OpenResty Regex
- Lua Built-in Patterns as a Regex Alternative
- Trace Regex Performance in Docker and Kubernetes
- How the Dynamic-Tracing Tools Work
- Tool Overhead: Zero Impact When Not Sampling
- FAQ: Nginx Regex Performance
Listing Loaded Lua Modules in OpenResty or Nginx Processes
- System Environment
- Names of Loaded Lua Modules
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
- System Environment
- Names of Loaded Lua Modules
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
Nginx High CPU Usage: Find Which Requests Consume the Most CPU
- Prerequisites and Environment Setup
- Find Which Request Hostname Uses the Most CPU
- Find Which Request URI Uses the Most CPU
- Digging Deeper: Why Some Hostnames Use More CPU
- Running the Tools in the Web Console
- Tracing Nginx CPU Usage Inside Containers
- How the CPU Profiling Tools Work
- The Overhead of the Profiling Tools
- Frequently Asked Questions
- Prerequisites and Environment Setup
- Find Which Request Hostname Uses the Most CPU
- Find Which Request URI Uses the Most CPU
- Digging Deeper: Why Some Hostnames Use More CPU
- Running the Tools in the Web Console
- Tracing Nginx CPU Usage Inside Containers
- How the CPU Profiling Tools Work
- The Overhead of the Profiling Tools
- Frequently Asked Questions
Configure HTTP Basic Auth in OpenResty Edge — No Server Reload or Restart
- Configure the HTTP basic auth credentials for applications
- Add a basic auth user group
- Enable basic auth with a page rule
- Test basic auth in a browser and with curl
- Configure global HTTP basic auth across all applications
- Add a global basic auth user group
- Configure the global auth for application
- Configure the HTTP basic auth credentials for applications
- Add a basic auth user group
- Enable basic auth with a page rule
- Test basic auth in a browser and with curl
- Configure global HTTP basic auth across all applications
- Add a global basic auth user group
- Configure the global auth for application
How to use custom dynamic metrics in OpenResty Edge
- Introduction to dynamic metrics
- Create custom dynamic metrics for the sample application
- Test
- Introduction to dynamic metrics
- Create custom dynamic metrics for the sample application
- Test
Limit Request Rate by Custom Keys in OpenResty Edge
- Add a request rate-limiting page rule in OpenResty Edge
- Test the rate limit with wrk
- Limit the rate of SSL/TLS handshakes
- OpenResty Edge rate limiting FAQ
- Add a request rate-limiting page rule in OpenResty Edge
- Test the rate limit with wrk
- Limit the rate of SSL/TLS handshakes
- OpenResty Edge rate limiting FAQ
Ylang in Production: Container Tracing, Stack Unwinding & Core Dumps (Series Part 4)
- Transparent Container Tracing
- Efficient Stack Unwinding
- Analyzing Dead Processes (Core Dumps)
- Very Low Tracing Overhead
- Standard Ylang Libraries & Tools
- Network Filtering & Control
- The Ylang Compiler’s Implementation
- Operating System Support
- Contributions to Open-Source Communities
- Transparent Container Tracing
- Efficient Stack Unwinding
- Analyzing Dead Processes (Core Dumps)
- Very Low Tracing Overhead
- Standard Ylang Libraries & Tools
- Network Filtering & Control
- The Ylang Compiler’s Implementation
- Operating System Support
- Contributions to Open-Source Communities
Ylang: Regex, Full Control Flow & Transparent Debug Symbol Handling (Series Part 3)
- The Language Syntax (Continued)
- String Literals
- Built-in Regex Support
- Full Control-Flow Support
- Floating-Point Number Support
- Compared to Open-Source Toolchains
- Transparent Debug Symbol Handling
- Debug Symbols: No Runtime Overhead
- Centralized Package Database
- Fuzzy Matching Debug Symbols
- The Language Syntax (Continued)
- String Literals
- Built-in Regex Support
- Full Control-Flow Support
- Floating-Point Number Support
- Compared to Open-Source Toolchains
- Transparent Debug Symbol Handling
- Debug Symbols: No Runtime Overhead
- Centralized Package Database
- Fuzzy Matching Debug Symbols
Ylang Syntax: Probes, Tracer/Tracee Spaces & Built-in Data Types (Series Part 2)
- The Language Syntax (Continued)
- Macros with Extensions
- Tracer and Tracee Spaces
- Probes
- Extended Variable Types
- The Language Syntax (Continued)
- Macros with Extensions
- Tracer and Tracee Spaces
- Probes
- Extended Variable Types
Ylang: A Dynamic Tracing Language for eBPF, SystemTap, GDB, and More (Part 1 of 4)
- What is Dynamic Tracing
- Why the “Y” Name
- Getting Started with Ylang
- Dynamic Tracing Backends: eBPF+, Stap+, GDB, and ODB
- Why a Unified Frontend Language for Dynamic Tracing
- The Ylang Syntax: Genuinely C-Compatible
- Frequently Asked Questions
- What is Dynamic Tracing
- Why the “Y” Name
- Getting Started with Ylang
- Dynamic Tracing Backends: eBPF+, Stap+, GDB, and ODB
- Why a Unified Frontend Language for Dynamic Tracing
- The Ylang Syntax: Genuinely C-Compatible
- Frequently Asked Questions
How to Release and Roll Back Gateway Config in OpenResty Edge: Version Control Without Reload
- Create a page rule for the sample application
- Release the page rule to all gateway clusters
- Test the released config with curl
- Modify the page rule
- Release the modified config
- Test the modified config
- Revert the latest config release
- Test the reverted config
- Roll back to any earlier release
- Create a page rule for the sample application
- Release the page rule to all gateway clusters
- Test the released config with curl
- Modify the page rule
- Release the modified config
- Test the modified config
- Revert the latest config release
- Test the reverted config
- Roll back to any earlier release
Set Different Host Headers for Upstream Requests in OpenResty Edge
- Before setting the Host header of the upstream request
- Set the Host header of the upstream request
- Test of the new page rule
- Before setting the Host header of the upstream request
- Set the Host header of the upstream request
- Test of the new page rule
Redirect Based on Browser Language in OpenResty Edge: Accept-Language Page Rule
- Redirect based on browser language with an Accept-Language page rule
- Match the root URI and the Accept-Language header with a regex
- Test the French redirect with curl
- Add a fallback rule that redirects other languages to English
- Ship changes to every gateway node with no Nginx reload
- Redirect based on browser language with an Accept-Language page rule
- Match the root URI and the Accept-Language header with a regex
- Test the French redirect with curl
- Add a fallback rule that redirects other languages to English
- Ship changes to every gateway node with no Nginx reload
OpenResty 1.19.9.1 released
- Version highlights
- Full Changelog
- Alpine 3.14 official release
- Version highlights
- Full Changelog
- Alpine 3.14 official release
Redirect HTTP to HTTPS in OpenResty Edge: 301 Page Rule to Enforce SSL
- Create a page rule to redirect all HTTP requests to HTTPS
- Release the 301 redirect rule to all gateway clusters
- Test the HTTP to HTTPS redirect with curl
- Create a page rule to redirect all HTTP requests to HTTPS
- Release the 301 redirect rule to all gateway clusters
- Test the HTTP to HTTPS redirect with curl
Automatic Let's Encrypt SSL Renewal, No Cron — OpenResty Edge
- Add the domains to your Edge application
- Issue and auto-renew a Let’s Encrypt SSL certificate
- Verify HTTPS and the Let’s Encrypt certificate on a gateway
- Add the domains to your Edge application
- Issue and auto-renew a Let’s Encrypt SSL certificate
- Verify HTTPS and the Let’s Encrypt certificate on a gateway
