Tencent Cloud Observability Platform
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Application Performance Management
- Pay-as-you-go (Postpaid)
- Packages (Prepaid)
- Mobile App Performance Monitoring
- Real User Monitoring
- Cloud Automated Testing
- Prometheus Monitoring
- Pay-as-You-Go (Postpaid)
- Quick Start
- EventBridge
- Cloud Product Monitoring
- Tencent Cloud Service Metrics
- Microservice
- Networking
- TencentDB
- TencentDB for Redis Monitoring Metrics
- CPM
- CDN And EdgeOne
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- CM Connection to Grafana
- Troubleshooting
- Application Performance Management
- Access Guide
- Accessing Go Application
- Accessing Java Application
- Accessing Python Application
- Accessing Node.js Application
- Accessing PHP Application
- Accessing .NET Application
- Operation Guide
- Resource Management
- Application Monitoring
- Application Diagnosis
- Database Call Monitoring
- Access Management
- Alarm Service
- System Configuration
- Associate Logs
- Inject TraceID Into Logs
- Practical Tutorial
- Parameter Information
- APM Data Protocol Standard
- Mobile App Performance Monitoring
- Access Guide
- Android Use Cases
- iOS Use Cases
- Tencent Cloud Real User Monitoring
- Operation Guide
- Application Management
- Access Management
- Resource Tag
- Connection Guide
- Web Use Cases
- Cloud Automated Testing
- Operation Guide
- Creating Test Task
- Testing Statistics
- Access Management
- References
- Testing Nodes
- FAQs
- Performance Testing Service
- Operation Guide
- Performance Testing in Script Mode
- Script Examples
- HTTP-based Performance Testing
- Performance Testing in JMeter Mode
- Project Management
- Scenario Management
- Advanced Configuration
- Export Stress Test Indicators
- Traffic Recording
- Performance Testing Report
- Access Control
- Alarm Management
- Tag Management
- Practice Tutorial
- JavaScript API List
- pts/http
- Response
- pts/dataset
- pts/grpc
- pts/jsonpath
- pts/redis
- pts/url
- URL
- pts/util
- pts/ws
- pts/socketio
- socketio
- pts/socket
- Prometheus Monitoring
- Product Introduction
- Access Guide
- EMR Integration
- Java Application Integration
- Exporter Integration
- Operation Guide
- Instance
- Recording Rule
- Alerting Rule
- Access Control
- TKE Metrics
- Practical Tutorial
- Terraform
- Grafana
- Operation Guide
- Instance
- Tencent Cloud Service Integration
- Plugin Management
- Dashboard
- Operation Guide
- Configuring Dashboard
- Monitoring Charts
- Creating Chart
- Use Cases of Different Chart Types
- Alarm Management
- Console Operation Guide
- Alarm Policy
- Configuring alert trigger conditions
- Alarm Notification
- Alarm Callback
- Alarm Receiving Channels and SMS Quota
- Dynamic Threshold Alarm
- Silencing Alarm
- EventBridge
- Product Introduction
- Practical Tutorial
- Migrating Event Alarm
- FAQs
- Related Agreements
- API Documentation
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- Notification Template APIs
- Legacy Alert APIs
- Prometheus Service APIs
- Grafana Service APIs
- Event Center APIs
- TencentCloud Managed Service for Prometheus APIs
- Monitoring APIs
DocumentationTencent Cloud Observability PlatformPerformance Testing ServiceJavaScript API Listpts/httpRequest
Request
Last updated: 2025-03-11 19:41:12
Request is the request structure when initiating a request.
Field
Field | Type | Description |
basicAuth? | BasicAuth | Basic authentication. |
body? | string, object, or ArrayBuffer. | The request body to be sent, which only needs to be specified when using the http.do method. |
chunked? | function，(body string) => void | When data is sent in a series of chunks, if the chunked function is specified, the response body will be read line by line and the callback function will be executed. |
contentLength? | number | Record the length of the associated content; -1 indicates unknown length, >=0 indicates the number of bytes that can be read from the body. |
discardResponseBody? | boolean | Discard the response body, suitable for scenarios where the response body is too large and the response body content does not need to be checked. |
headers? | Record<string, string> | Request header. |
host? | string | host or host:port. |
maxRedirects? | number | The maximum number of redirects. |
method? | string | Specify the HTTP method, such as GET, PUT, and POST. It only needs to be specified when using the http.do method. |
path? | string | The path; leading slashes are omitted for relative paths. |
query? | Record<string, string> | URL parameters sent with the request. |
scheme? | "http" | "https" | Protocol, "http" or "https" should be filled in. |
service? | string | In PTS, different services are identified based on the URL, and reports are generated based on this dimension. For example, when the URL is http://demo.com/{id}, different IDs will be recognized as different services. By specifying the service, such requests can be categorized under the same service in the report. |
timeout? | number | The time limit for requests issued by the client, where the timeout period in milliseconds includes connection time, any redirects, and reading the response body. |
url? | string | The URL to be accessed, which only needs to be specified when using the do method. |
Samples
Use Request in the http.do method:
import http from 'pts/http';export default function () {const req = {method: 'post',url: 'http://httpbin.org/post',headers: { 'Content-Type': 'application/json' },query: { a: '1' },body: { user_id: '12345' },};const resp = http.do(req);console.log(resp.json().args.a); // 1console.log(resp.json().json.user_id); // 12345}
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No