All Products
Search
Document Center

Application Real-Time Monitoring Service:Trace Explorer parameters

Last Updated:Mar 11, 2026

Trace Explorer in Application Real-Time Monitoring Service (ARMS) uses the OpenTelemetry tracing data model. The following tables list the parameters available on each span, grouped by category.

Identity

ParameterDescription
traceIdUnique identifier of the trace
spanIdUnique identifier of the span within a trace
parentSpanIdID of the parent span. Identifies the caller in a parent-child span relationship
spanNameName of the span
serviceNameName of the service that generated the span. Used for multitenancy

Timing

ParameterDescription
startTimeSpan start time, in nanoseconds
durationSpan duration, in nanoseconds

Status

ParameterDescription
statusCodeStatus of the span. See statusCode values below
statusMessageHuman-readable message that describes the status code

statusCode values

ValueConstantMeaning
0STATUS_CODE_UNSETThe span is not configured
1STATUS_CODE_OKThe span is running as expected
2STATUS_CODE_ERRORA span error has occurred

Classification

ParameterDescription
kindRole of the span in a distributed trace, as defined by the OpenTelemetry SpanKind specification. See kind values below
serviceTypeNumeric identifier of the framework or component that generated the span. See serviceType values below

kind values

The kind parameter classifies the role of a span in a distributed trace, distinguishing between incoming requests, outgoing calls, and asynchronous messaging.

ValueConstantMeaning
0SPAN_KIND_UNSPECIFIEDDefault value when no kind is set
1SPAN_KIND_INTERNALInternal operation within a service, such as a function call
2SPAN_KIND_SERVERServer-side handling of a synchronous request, such as an HTTP or RPC server
3SPAN_KIND_CLIENTClient-side of a synchronous request to a remote service
4SPAN_KIND_PRODUCERSender in an asynchronous messaging system, such as a message queue producer
5SPAN_KIND_CONSUMERReceiver in an asynchronous messaging system, such as a message queue consumer

For the full specification, see OpenTelemetry SpanKind.

Infrastructure

ParameterDescription
hostnameHostname of the machine that generated the span
ipIP address of the host

Payload

ParameterDescription
attributesIndexed key-value pairs attached to the span for filtering and querying
resourcesResource metadata about the span, such as the process ID and Java Virtual Machine (JVM) version
eventEvent recorded during the span lifecycle. Contains unindexed fields such as timestamp, name, and attribute
linksLinks from the current span to one or more spans in the same or different traces

serviceType values

The serviceType parameter identifies the framework or component that generated a span. Use these numeric codes to filter traces by technology stack.

Web servers and application servers

ValueFramework
1010Tomcat
1030Jetty Server
1040Akka HTTP
1060WebSphere
1080WebLogic
1090Undertow

RPC frameworks

ValueFramework
1101gRPC Server
9101gRPC Client
1110Dubbo Provider
9110Dubbo Consumer
1111HSF Provider
9111HSF Consumer

Scheduled tasks

ValueFramework
1301SchedulerX
1302XXL-JOB
1303Spring Scheduled
1304Quartz
1305ElasticJob

Databases

ValueDatabase
2100MySQL
2150MariaDB
2300Oracle
2500PostgreSQL
2510PPAS
2520SQL Server
2650MongoDB
2700OceanBase
2780ClickHouse
2800InfluxDB
2900Cassandra
2910Lindorm

Web frameworks and ORM

ValueFramework
5053Spring Webflux
5510MyBatis

Connection pools

ValueFramework
6060HikariCP
6062Druid

Search engines

ValueEngine
72Elasticsearch

Cache and Redis clients

ValueClient
8050Memcached
8200Jedis
8201Lettuce
8203Redisson

Message queues

ValueFramework
8410RocketMQ Producer
8420RocketMQ Consumer
8660Kafka Producer
8670Kafka Consumer

HTTP clients

ValueClient
1035Jetty Client
1142Reactor Netty HTTP Client
9050Apache HTTP Client 3
9052Apache HTTP Client 4
9054Google HTTP Client
9055JDK HttpURLConnection
9056AsyncHttpClient
9058OkHttpClient
9130Vertx HTTP Client
9153Spring Webflux Client

Network frameworks

ValueFramework
9150Netty
9151Netty Client

See also