Release Notes
Latest Version: v0.2.7
2025-09-02
v0.2.7
Feature Added option to process Span data sequentially
- When processing
scopespanof Trace data,Span.Kind = KIND_SERVERis handled as a WhaTap transaction - Previous behavior: aggregated multiple
KIND_SERVERspans in a single request and processed them at the end - With the option enabled, spans are processed sequentially
- otel_tx_process_server_span_in_order_enabled
- Default:
false
2025-09-01
v0.2.6
Change Improved Span data processing method
- Collect span data in a parent–child tree structure
- Changed to process subsequent child spans even if an intermediate parent span is missing
Change Added attribute key names
-
Added the attribute key name
http.response.status_codefor collecting HTTP status codes- otel_attr_tx_status_keys
- Default:
http.status_code, http.response.status_code
- Default:
- otel_attr_tx_status_keys
-
Added the attribute key name
errorfor collecting error information- otel_attr_error_keys
- Default:
error, error.type
- Default:
- otel_attr_error_keys
2025-07-09
v0.2.5
Feature Treat spans without a parent as transactions
- A span with no parent is treated as a transaction regardless of kind
- Previously, only
SPAN_KIND_SERVERwas treated as a transaction - Related option:
otel_tx_root_span_enabled(Default: true)
Feature Improved metrics collection method
- Changed from log-based collection to a Prometheus-compatible approach
- Viewable on Flex Board (MXQL data query)
Change Changed behavior of query_string_enabled option
- If
query_string_enabledis true andquery_string_urlsandquery_string_keysare not set,
collect query strings for all URLs
Fixed Fixed an issue with HTTP status counter collection
- Fixed an issue where the sum of 5xx errors was not collected
2025-04-30
v0.2.4
Feature Mark HTTP status errors
-
Setting to mark as error when HTTP status code is 400 or higher
- Key: transaction_status_error_enable
- Type: bool
- Default:
false - Collection interval: 10 seconds
Feature Collect HTTP status code statistics
-
Setting to collect counts by status code across all URLs
- Key: tx_status_meter_enabled
- Type: bool
- Default:
true - Collection interval: 10 seconds
-
Setting to collect counts by status code per URL
- Key: stat_txstatus_enabled
- Type: bool
- Default:
true - Collection interval: 5 minutes
Feature Analyze distributed traces by configuring virtual HTTP call spans
-
Enable virtual spans when HTTP call span information is missing
- Key: otel_virtual_httpc_enabled
- Type: bool
- Default:
false
-
Set the name when HTTP call span information is missing
- Key: otel_virtual_httpc_name
- Type: string
- Default:
external http call
Fixed Fixed an error in the HTTP Method ignore setting
PATCH,OPTIONS,HEAD, andTRACEmethods are not collected as transactions
2025-02-25
v0.2.3
Feature Added an option to set the transaction name from the span name value
- otel_tx_path_setby_name_enabled bool (Default
false)
Feature Added options for multi-transaction linkage recognizing a trace span’s SpanID as the external connection’s ParentSpanID
- otel_mtrace_stepid_setby_trace_spanid_enabled bool (Default
false)
Feature Added a log option to output the same content to Stdout as the file log
- log_stdout_enabled bool (Default
false)
Fixed Fixed an issue where a “file not found” error log was repeatedly printed if whatap.conf did not exist
Fixed Fixed an issue where the transaction ID was shown as 0
2024-12-11
v0.2.2
Feature Process transaction URL and URI information separately
Items previously labeled as URL are now labeled as URI.
Feature Modified external HTTP call URL notation to "Host:Port"
Feature Added default attribute keys for extracting Kong gateway information
2024-11-06
v0.2.1
Fixed Fixed an issue where a goroutine stopped due to an unexpected internal panic
Fixed Removed and cleaned up unnecessary logs
2024-06-19
v0.2.0
New Support for Linux aarch64
New Collect additional error information from span events
-
Collect when error information comes in as an
eventrather than anattribute. -
Add agent configuration options to find errors in
event.whatap.confotel_events_exception_keys=exception.type
otel_events_error_message_keys=exception.message
otel_events_error_stack_keys=exception.stacktrace
otel_events_error_esc_keys=exception.escaped
Changed Use security.conf instead of paramkey.txt
Use the value of the paramkey key in the existing security.conf file. Changed the default from a random value to WHATAP. When set to WHATAP, decryption can be done without entering a key.
Changed Changed SQL normalization option settings
-
Always enable parameter separation and normalization in SQL statements. Set
trace_sql_normalize_enabledtotrueat all times. -
If normalization was previously disabled, enable the setting to normalize and record parameters separately.
- Set
profile_sql_param_enabledtotrue. - Collect normalized parameters with separate encryption.
- You can decrypt and view data using
paramkeyin security.conf.
- Set