-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Major
-
None
-
Affects Version/s: 7.0.28
-
Component/s: Frontend (F), Packages (C), Proxy (P)
-
None
Summary
Currently, the maximum supported length for Web Scenario (httptest.name) and Web Scenario Step (httpstep.name) names is limited to 64 characters.
While this limit may have been sufficient when originally introduced, modern web monitoring frequently involves long REST API endpoints, descriptive business transaction names, cloud-native services, and microservice architectures where meaningful identifiers often exceed 64 characters.
I would like to request increasing the supported length of both Web Scenario and Web Scenario Step names to at least 512 characters (or 1024 if considered acceptable).
Current Behaviour
- Web Scenario names are limited to 64 characters.
- Web Scenario Step names are limited to 64 characters.
- The same limit is enforced throughout the product (frontend, API, server, proxy and database schema).
Because of this limitation, users must abbreviate names, reducing readability and making configurations harder to maintain.
Requested Enhancement
Increase the supported maximum length for:
| Object | Current | Requested |
|---|---|---|
| Web Scenario name (httptest.name) | 64 | 512 (or 1024) |
| Web Scenario Step name (httpstep.name) | 64 | 512 (or 1024) |
The new limit should be consistently supported across all components, including:
- Frontend validation
- API validation
- Database schema
- Server validation
- Proxy validation
- Configuration synchronization
- Configuration cache
- Import/Export
- Template import
- Discovery and configuration processing
Why this enhancement is needed
In many enterprise environments, Web Scenarios are used to monitor complex REST APIs and business transactions rather than simple web pages.
Typical naming conventions include:
- Complete business transaction names
- Service identifiers
- Environment information
- API version
- Region or tenant information
- Descriptive endpoint names
These names frequently exceed the current 64-character limit.
For example:
Production - Customer Order Management API - Validate Payment Authorization - EU-West - v3
or
POST /api/v3/customer/orders/{orderId}/payment/authorization/validate
Using descriptive names significantly improves:
- configuration readability
- troubleshooting
- dashboard usability
- operational maintenance
- template portability
The current limitation forces administrators to shorten names, making configurations less intuitive, especially in environments with hundreds or thousands of Web Scenarios.
Background
In previous Zabbix versions, extending the supported length through local customization was relatively straightforward. In newer releases, the limit is enforced across multiple components (frontend, server, proxy, configuration cache and synchronization), making such extensions impractical without modifying several parts of the code base.
Rather than maintaining custom patches, it would be beneficial if Zabbix officially supported longer Web Scenario and Web Scenario Step names.
https://support.zabbix.com/browse/ZBX-27923
Expected Result
Zabbix should officially support Web Scenario and Web Scenario Step names of at least 512 characters, with the new limit applied consistently throughout the product so that configuration, synchronization, import/export and monitoring work without additional customization.