307 lines
26 KiB
Plaintext
307 lines
26 KiB
Plaintext
# UI中的服务名称
|
||
# ${service name} = [${group name }::]${logic name}
|
||
# 组名仅是可选的。
|
||
agent.service_name=${SW_AGENT_NAME:Your_ApplicationName}
|
||
agent.service_name#length=${SW_AGENT_NAME_MAX_LENGTH:50}
|
||
|
||
# 代理命名空间
|
||
agent.namespace=${SW_AGENT_NAMESPACE:}
|
||
|
||
# 代理集群
|
||
agent.cluster=${SW_AGENT_CLUSTER:}
|
||
|
||
# 每3秒采样的轨迹数
|
||
# 负或零表示关闭，默认情况下
|
||
agent.sample_n_per_3_secs=${SW_AGENT_SAMPLE:-1}
|
||
|
||
# 身份验证活动基于后端设置，请参阅application.yml了解更多细节。
|
||
agent.authentication=${SW_AGENT_AUTHENTICATION:}
|
||
|
||
# 单个跨度中TraceSegmentRef的最大数量，以保持内存成本可估算。
|
||
agent.trace_segment_ref_limit_per_span=${SW_TRACE_SEGMENT_LIMIT:500}
|
||
|
||
# 单个段中跨度的最大数量。
|
||
# 通过这个配置项，SkyWalking保持你的应用内存成本估计。
|
||
agent.span_limit_per_segment=${SW_AGENT_SPAN_LIMIT:300}
|
||
|
||
#如果第一个span的操作名包含在此集合中，则应忽略此段。多个值应该用‘，’隔开。
|
||
agent.ignore_suffix=${SW_AGENT_IGNORE_SUFFIX:.jpg,.jpeg,.js,.css,.png,.bmp,.gif,.ico,.mp3,.mp4,.html,.svg}
|
||
|
||
# 如果为true，则SkyWalking代理将所有检测的类文件保存在 “/debugging” 文件夹中。
|
||
# SkyWalking团队可能会要求这些文件以解决兼容问题。
|
||
agent.is_open_debugging_class=${SW_AGENT_OPEN_DEBUG:false}
|
||
|
||
# 实例名是实例的标识，在服务中唯一。如果空着，空中行走代理将
|
||
# 生成32位uuid。默认情况下，SkyWalking使用UUID @ hostname作为实例名称。最大长度为50(UTF-8字符)
|
||
agent.instance_name=${SW_AGENT_INSTANCE_NAME:}
|
||
agent.instance_name#length=${SW_AGENT_INSTANCE_NAME_MAX_LENGTH:50}
|
||
|
||
# json格式的服务实例属性。例如agent.instance_properties_json = {"org": "apache-skywalking"}
|
||
agent.instance_properties_json=${SW_INSTANCE_PROPERTIES_JSON:}
|
||
|
||
# 代理的深度如何，记录时都会导致异常。
|
||
agent.cause_exception_depth=${SW_AGENT_CAUSE_EXCEPTION_DEPTH:5}
|
||
|
||
# 强制grpc的重连接周期，基于grpc_channel_check_interval。
|
||
agent.force_reconnection_period=${SW_AGENT_FORCE_RECONNECTION_PERIOD:1}
|
||
|
||
# operationName最大长度
|
||
# 注意，在目前的实践中，我们不建议长度超过190。
|
||
agent.operation_name_threshold=${SW_AGENT_OPERATION_NAME_THRESHOLD:150}
|
||
|
||
# 如果此值为true，即使后端不可用，也要继续跟踪。
|
||
agent.keep_tracing=${SW_AGENT_KEEP_TRACING:false}
|
||
|
||
# 代理默认使用gRPC纯文本。
|
||
# 如果为true，即使没有检测到CA文件，SkyWalking代理也使用TLS。
|
||
agent.force_tls=${SW_AGENT_FORCE_TLS:false}
|
||
|
||
# gRPC SSL可信ca文件。
|
||
agent.ssl_trusted_ca_path=${SW_AGENT_SSL_TRUSTED_CA_PATH:/ca/ca.crt}
|
||
|
||
# 当存在ssl_key_path和ssl_cert_chain_path时，启用mTLS。
|
||
agent.ssl_key_path=${SW_AGENT_SSL_KEY_PATH:}
|
||
|
||
agent.ssl_cert_chain_path=${SW_AGENT_SSL_CERT_CHAIN_PATH:}
|
||
|
||
# 启用代理内核服务和检测。
|
||
agent.enable=${SW_AGENT_ENABLE:true}
|
||
|
||
# 限制ipv4列表大小的长度。
|
||
osinfo.ipv4_list_size=${SW_AGENT_OSINFO_IPV4_LIST_SIZE:10}
|
||
|
||
# grpc信道状态检查间隔。
|
||
collector.grpc_channel_check_interval=${SW_AGENT_COLLECTOR_GRPC_CHANNEL_CHECK_INTERVAL:30}
|
||
# 代理心跳报告期。第二小队。
|
||
collector.heartbeat_period=${SW_AGENT_COLLECTOR_HEARTBEAT_PERIOD:10}
|
||
# agent将实例属性发送到后端
|
||
# collector.heartbeat_period * collector.properties_report_period_factor秒
|
||
collector.properties_report_period_factor=${SW_AGENT_COLLECTOR_PROPERTIES_REPORT_PERIOD_FACTOR:5}
|
||
# 后端服务地址。
|
||
collector.backend_service=${SW_AGENT_COLLECTOR_BACKEND_SERVICES:192.168.138.130:11800}
|
||
# grpc客户端向上游发送数据的超时时间。单位是秒。
|
||
collector.grpc_upstream_timeout=${SW_AGENT_COLLECTOR_GRPC_UPSTREAM_TIMEOUT:30}
|
||
# 嗅探器获取配置文件任务列表间隔。
|
||
collector.get_profile_task_interval=${SW_AGENT_COLLECTOR_GET_PROFILE_TASK_INTERVAL:20}
|
||
# 嗅探器获取代理动态配置间隔。
|
||
collector.get_agent_dynamic_config_interval=${SW_AGENT_COLLECTOR_GET_AGENT_DYNAMIC_CONFIG_INTERVAL:20}
|
||
# 如果为true，skywalking代理将启用定期解析DNS以更新接收方服务地址。
|
||
collector.is_resolve_dns_periodically=${SW_AGENT_COLLECTOR_IS_RESOLVE_DNS_PERIODICALLY:false}
|
||
|
||
# Logging level
|
||
logging.level=${SW_LOGGING_LEVEL:INFO}
|
||
# Logging file_name
|
||
logging.file_name=${SW_LOGGING_FILE_NAME:skywalking-api.log}
|
||
# Log output. Default is FILE. Use CONSOLE means output to stdout.
|
||
logging.output=${SW_LOGGING_OUTPUT:FILE}
|
||
# Log files directory. Default is blank string, meaning use "{theSkywalkingAgentJarDir}/logs " to output logs.
|
||
# {theSkywalkingAgentJarDir} is the directory where the skywalking agent jar file is located
|
||
logging.dir=${SW_LOGGING_DIR:}
|
||
# Logger resolver: PATTERN or JSON. The default is PATTERN, which uses logging.pattern to print traditional text logs.
|
||
# JSON resolver prints logs in JSON format.
|
||
logging.resolver=${SW_LOGGING_RESOLVER:PATTERN}
|
||
# Logging format. There are all conversion specifiers:
|
||
# * %level means log level.
|
||
# * %timestamp means now of time with format yyyy-MM-dd HH:mm:ss:SSS.
|
||
# * %thread means name of current thread.
|
||
# * %msg means some message which user logged.
|
||
# * %class means SimpleName of TargetClass.
|
||
# * %throwable means a throwable which user called.
|
||
# * %agent_name means agent.service_name. Only apply to the PatternLogger.
|
||
logging.pattern=${SW_LOGGING_PATTERN:%level %timestamp %thread %class : %msg %throwable}
|
||
# Logging max_file_size, default: 300 * 1024 * 1024 = 314572800
|
||
logging.max_file_size=${SW_LOGGING_MAX_FILE_SIZE:314572800}
|
||
# The max history log files. When rollover happened, if log files exceed this number,
|
||
# then the oldest file will be delete. Negative or zero means off, by default.
|
||
logging.max_history_files=${SW_LOGGING_MAX_HISTORY_FILES:-1}
|
||
|
||
# Listed exceptions would not be treated as an error. Because in some codes, the exception is being used as a way of controlling business flow.
|
||
# Besides, the annotation named IgnoredException in the trace toolkit is another way to configure ignored exceptions.
|
||
statuscheck.ignored_exceptions=${SW_STATUSCHECK_IGNORED_EXCEPTIONS:}
|
||
# The max recursive depth when checking the exception traced by the agent. Typically, we don't recommend setting this more than 10, which could cause a performance issue. Negative value and 0 would be ignored, which means all exceptions would make the span tagged in error status.
|
||
statuscheck.max_recursive_depth=${SW_STATUSCHECK_MAX_RECURSIVE_DEPTH:1}
|
||
|
||
# Max element count in the correlation context
|
||
correlation.element_max_number=${SW_CORRELATION_ELEMENT_MAX_NUMBER:3}
|
||
|
||
# Max value length of each element.
|
||
correlation.value_max_length=${SW_CORRELATION_VALUE_MAX_LENGTH:128}
|
||
# Tag the span by the key/value in the correlation context, when the keys listed here exist.
|
||
correlation.auto_tag_keys=${SW_CORRELATION_AUTO_TAG_KEYS:}
|
||
# The buffer size of collected JVM info.
|
||
jvm.buffer_size=${SW_JVM_BUFFER_SIZE:600}
|
||
# The period in seconds of JVM metrics collection. Unit is second.
|
||
jvm.metrics_collect_period=${SW_JVM_METRICS_COLLECT_PERIOD:1}
|
||
# The buffer channel size.
|
||
buffer.channel_size=${SW_BUFFER_CHANNEL_SIZE:5}
|
||
# The buffer size.
|
||
buffer.buffer_size=${SW_BUFFER_BUFFER_SIZE:300}
|
||
# If true, skywalking agent will enable profile when user create a new profile task. Otherwise disable profile.
|
||
profile.active=${SW_AGENT_PROFILE_ACTIVE:true}
|
||
# Parallel monitor endpoint thread count
|
||
profile.max_parallel=${SW_AGENT_PROFILE_MAX_PARALLEL:5}
|
||
# Max monitoring sub-tasks count of one single endpoint access
|
||
profile.max_accept_sub_parallel=${SW_AGENT_PROFILE_MAX_ACCEPT_SUB_PARALLEL:5}
|
||
# Max monitor segment time(minutes), if current segment monitor time out of limit, then stop it.
|
||
profile.duration=${SW_AGENT_PROFILE_DURATION:10}
|
||
# Max dump thread stack depth
|
||
profile.dump_max_stack_depth=${SW_AGENT_PROFILE_DUMP_MAX_STACK_DEPTH:500}
|
||
# Snapshot transport to backend buffer size
|
||
profile.snapshot_transport_buffer_size=${SW_AGENT_PROFILE_SNAPSHOT_TRANSPORT_BUFFER_SIZE:4500}
|
||
# If true, the agent collects and reports metrics to the backend.
|
||
meter.active=${SW_METER_ACTIVE:true}
|
||
# Report meters interval. The unit is second
|
||
meter.report_interval=${SW_METER_REPORT_INTERVAL:20}
|
||
# Max size of the meter pool
|
||
meter.max_meter_size=${SW_METER_MAX_METER_SIZE:500}
|
||
# The max size of message to send to server.Default is 10 MB
|
||
log.max_message_size=${SW_GRPC_LOG_MAX_MESSAGE_SIZE:10485760}
|
||
|
||
# Mount the specific folders of the plugins. Plugins in mounted folders would work.
|
||
plugin.mount=${SW_MOUNT_FOLDERS:plugins,activations}
|
||
# Peer maximum description limit.
|
||
plugin.peer_max_length=${SW_PLUGIN_PEER_MAX_LENGTH:200}
|
||
# Exclude some plugins define in plugins dir.Plugin names is defined in [Agent plugin list](Plugin-list.md)
|
||
plugin.exclude_plugins=${SW_EXCLUDE_PLUGINS:}
|
||
# If true, trace all the parameters in MongoDB access, default is false. Only trace the operation, not include parameters.
|
||
plugin.mongodb.trace_param=${SW_PLUGIN_MONGODB_TRACE_PARAM:false}
|
||
# If set to positive number, the `WriteRequest.params` would be truncated to this length, otherwise it would be completely saved, which may cause performance problem.
|
||
plugin.mongodb.filter_length_limit=${SW_PLUGIN_MONGODB_FILTER_LENGTH_LIMIT:256}
|
||
# If true, trace all the DSL(Domain Specific Language) in ElasticSearch access, default is false.
|
||
plugin.elasticsearch.trace_dsl=${SW_PLUGIN_ELASTICSEARCH_TRACE_DSL:false}
|
||
# If true, the fully qualified method name will be used as the endpoint name instead of the request URL, default is false.
|
||
plugin.springmvc.use_qualified_name_as_endpoint_name=${SW_PLUGIN_SPRINGMVC_USE_QUALIFIED_NAME_AS_ENDPOINT_NAME:false}
|
||
# If true, the fully qualified method name will be used as the operation name instead of the given operation name, default is false.
|
||
plugin.toolkit.use_qualified_name_as_operation_name=${SW_PLUGIN_TOOLKIT_USE_QUALIFIED_NAME_AS_OPERATION_NAME:false}
|
||
# If set to true, the parameters of the sql (typically `java.sql.PreparedStatement`) would be collected.
|
||
plugin.jdbc.trace_sql_parameters=${SW_JDBC_TRACE_SQL_PARAMETERS:false}
|
||
# If set to positive number, the `db.sql.parameters` would be truncated to this length, otherwise it would be completely saved, which may cause performance problem.
|
||
plugin.jdbc.sql_parameters_max_length=${SW_PLUGIN_JDBC_SQL_PARAMETERS_MAX_LENGTH:512}
|
||
# If set to positive number, the `db.statement` would be truncated to this length, otherwise it would be completely saved, which may cause performance problem.
|
||
plugin.jdbc.sql_body_max_length=${SW_PLUGIN_JDBC_SQL_BODY_MAX_LENGTH:2048}
|
||
# If true, trace all the query parameters(include deleteByIds and deleteByQuery) in Solr query request, default is false.
|
||
plugin.solrj.trace_statement=${SW_PLUGIN_SOLRJ_TRACE_STATEMENT:false}
|
||
# If true, trace all the operation parameters in Solr request, default is false.
|
||
plugin.solrj.trace_ops_params=${SW_PLUGIN_SOLRJ_TRACE_OPS_PARAMS:false}
|
||
# If true, trace all middleware/business handlers that are part of the Light4J handler chain for a request.
|
||
plugin.light4j.trace_handler_chain=${SW_PLUGIN_LIGHT4J_TRACE_HANDLER_CHAIN:false}
|
||
# If true, the transaction definition name will be simplified.
|
||
plugin.springtransaction.simplify_transaction_definition_name=${SW_PLUGIN_SPRINGTRANSACTION_SIMPLIFY_TRANSACTION_DEFINITION_NAME:false}
|
||
# Threading classes (`java.lang.Runnable` and `java.util.concurrent.Callable`) and their subclasses, including anonymous inner classes whose name match any one of the `THREADING_CLASS_PREFIXES` (splitted by `,`) will be instrumented, make sure to only specify as narrow prefixes as what you're expecting to instrument, (`java.` and `javax.` will be ignored due to safety issues)
|
||
plugin.jdkthreading.threading_class_prefixes=${SW_PLUGIN_JDKTHREADING_THREADING_CLASS_PREFIXES:}
|
||
# This config item controls that whether the Tomcat plugin should collect the parameters of the request. Also, activate implicitly in the profiled trace.
|
||
plugin.tomcat.collect_http_params=${SW_PLUGIN_TOMCAT_COLLECT_HTTP_PARAMS:false}
|
||
# This config item controls that whether the SpringMVC plugin should collect the parameters of the request, when your Spring application is based on Tomcat, consider only setting either `plugin.tomcat.collect_http_params` or `plugin.springmvc.collect_http_params`. Also, activate implicitly in the profiled trace.
|
||
plugin.springmvc.collect_http_params=${SW_PLUGIN_SPRINGMVC_COLLECT_HTTP_PARAMS:false}
|
||
# This config item controls that whether the HttpClient plugin should collect the parameters of the request
|
||
plugin.httpclient.collect_http_params=${SW_PLUGIN_HTTPCLIENT_COLLECT_HTTP_PARAMS:false}
|
||
# When `COLLECT_HTTP_PARAMS` is enabled, how many characters to keep and send to the OAP backend, use negative values to keep and send the complete parameters, NB. this config item is added for the sake of performance.
|
||
plugin.http.http_params_length_threshold=${SW_PLUGIN_HTTP_HTTP_PARAMS_LENGTH_THRESHOLD:1024}
|
||
# When `include_http_headers` declares header names, this threshold controls the length limitation of all header values. use negative values to keep and send the complete headers. Note. this config item is added for the sake of performance.
|
||
plugin.http.http_headers_length_threshold=${SW_PLUGIN_HTTP_HTTP_HEADERS_LENGTH_THRESHOLD:2048}
|
||
# Set the header names, which should be collected by the plugin. Header name must follow `jakarta.servlet.http` definition. Multiple names should be split by comma.
|
||
plugin.http.include_http_headers=${SW_PLUGIN_HTTP_INCLUDE_HTTP_HEADERS:}
|
||
# This config item controls that whether the Feign plugin should collect the http body of the request.
|
||
plugin.feign.collect_request_body=${SW_PLUGIN_FEIGN_COLLECT_REQUEST_BODY:false}
|
||
# When `COLLECT_REQUEST_BODY` is enabled, how many characters to keep and send to the OAP backend, use negative values to keep and send the complete body.
|
||
plugin.feign.filter_length_limit=${SW_PLUGIN_FEIGN_FILTER_LENGTH_LIMIT:1024}
|
||
# When `COLLECT_REQUEST_BODY` is enabled and content-type start with SUPPORTED_CONTENT_TYPES_PREFIX, collect the body of the request , multiple paths should be separated by `,`
|
||
plugin.feign.supported_content_types_prefix=${SW_PLUGIN_FEIGN_SUPPORTED_CONTENT_TYPES_PREFIX:application/json,text/}
|
||
# If true, trace all the influxql(query and write) in InfluxDB access, default is true.
|
||
plugin.influxdb.trace_influxql=${SW_PLUGIN_INFLUXDB_TRACE_INFLUXQL:true}
|
||
# Apache Dubbo consumer collect `arguments` in RPC call, use `Object#toString` to collect `arguments`.
|
||
plugin.dubbo.collect_consumer_arguments=${SW_PLUGIN_DUBBO_COLLECT_CONSUMER_ARGUMENTS:false}
|
||
# When `plugin.dubbo.collect_consumer_arguments` is `true`, Arguments of length from the front will to the OAP backend
|
||
plugin.dubbo.consumer_arguments_length_threshold=${SW_PLUGIN_DUBBO_CONSUMER_ARGUMENTS_LENGTH_THRESHOLD:256}
|
||
# Apache Dubbo provider collect `arguments` in RPC call, use `Object#toString` to collect `arguments`.
|
||
plugin.dubbo.collect_provider_arguments=${SW_PLUGIN_DUBBO_COLLECT_PROVIDER_ARGUMENTS:false}
|
||
# When `plugin.dubbo.collect_provider_arguments` is `true`, Arguments of length from the front will to the OAP backend
|
||
plugin.dubbo.provider_arguments_length_threshold=${SW_PLUGIN_DUBBO_PROVIDER_ARGUMENTS_LENGTH_THRESHOLD:256}
|
||
# A list of host/port pairs to use for establishing the initial connection to the Kafka cluster.
|
||
plugin.kafka.bootstrap_servers=${SW_KAFKA_BOOTSTRAP_SERVERS:localhost:9092}
|
||
# Timeout period of reading topics from the Kafka server, the unit is second.
|
||
plugin.kafka.get_topic_timeout=${SW_GET_TOPIC_TIMEOUT:10}
|
||
# Kafka producer configuration. Read [producer configure](http://kafka.apache.org/24/documentation.html#producerconfigs)
|
||
# to get more details. Check document for more details and examples.
|
||
plugin.kafka.producer_config=${SW_PLUGIN_KAFKA_PRODUCER_CONFIG:}
|
||
# Configure Kafka Producer configuration in JSON format. Notice it will be overridden by plugin.kafka.producer_config[key], if the key duplication.
|
||
plugin.kafka.producer_config_json=${SW_PLUGIN_KAFKA_PRODUCER_CONFIG_JSON:}
|
||
# Specify which Kafka topic name for Meter System data to report to.
|
||
plugin.kafka.topic_meter=${SW_PLUGIN_KAFKA_TOPIC_METER:skywalking-meters}
|
||
# Specify which Kafka topic name for JVM metrics data to report to.
|
||
plugin.kafka.topic_metrics=${SW_PLUGIN_KAFKA_TOPIC_METRICS:skywalking-metrics}
|
||
# Specify which Kafka topic name for traces data to report to.
|
||
plugin.kafka.topic_segment=${SW_PLUGIN_KAFKA_TOPIC_SEGMENT:skywalking-segments}
|
||
# Specify which Kafka topic name for Thread Profiling snapshot to report to.
|
||
plugin.kafka.topic_profiling=${SW_PLUGIN_KAFKA_TOPIC_PROFILINGS:skywalking-profilings}
|
||
# Specify which Kafka topic name for the register or heartbeat data of Service Instance to report to.
|
||
plugin.kafka.topic_management=${SW_PLUGIN_KAFKA_TOPIC_MANAGEMENT:skywalking-managements}
|
||
# Specify which Kafka topic name for the logging data to report to.
|
||
plugin.kafka.topic_logging=${SW_PLUGIN_KAFKA_TOPIC_LOGGING:skywalking-logs}
|
||
# isolate multi OAP server when using same Kafka cluster (final topic name will append namespace before Kafka topics with `-` ).
|
||
plugin.kafka.namespace=${SW_KAFKA_NAMESPACE:}
|
||
# Specify which class to decode encoded configuration of kafka.You can set encoded information in `plugin.kafka.producer_config_json` or `plugin.kafka.producer_config` if you need.
|
||
plugin.kafka.decode_class=${SW_KAFKA_DECODE_CLASS:}
|
||
# Match spring beans with regular expression for the class name. Multiple expressions could be separated by a comma. This only works when `Spring annotation plugin` has been activated.
|
||
plugin.springannotation.classname_match_regex=${SW_SPRINGANNOTATION_CLASSNAME_MATCH_REGEX:}
|
||
# Whether or not to transmit logged data as formatted or un-formatted.
|
||
plugin.toolkit.log.transmit_formatted=${SW_PLUGIN_TOOLKIT_LOG_TRANSMIT_FORMATTED:true}
|
||
# If set to true, the parameters of Redis commands would be collected by Lettuce agent.
|
||
plugin.lettuce.trace_redis_parameters=${SW_PLUGIN_LETTUCE_TRACE_REDIS_PARAMETERS:false}
|
||
# If set to positive number and `plugin.lettuce.trace_redis_parameters` is set to `true`, Redis command parameters would be collected and truncated to this length.
|
||
plugin.lettuce.redis_parameter_max_length=${SW_PLUGIN_LETTUCE_REDIS_PARAMETER_MAX_LENGTH:128}
|
||
# Specify which command should be converted to write operation
|
||
plugin.lettuce.operation_mapping_write=${SW_PLUGIN_LETTUCE_OPERATION_MAPPING_WRITE:getset,set,setbit,setex,setnx,setrange,strlen,mset,msetnx,psetex,incr,incrby,incrbyfloat,decr,decrby,append,hmset,hset,hsetnx,hincrby,hincrbyfloat,hdel,rpoplpush,rpush,rpushx,lpush,lpushx,lrem,ltrim,lset,brpoplpush,linsert,sadd,sdiff,sdiffstore,sinterstore,sismember,srem,sunion,sunionstore,sinter,zadd,zincrby,zinterstore,zrange,zrangebylex,zrangebyscore,zrank,zrem,zremrangebylex,zremrangebyrank,zremrangebyscore,zrevrange,zrevrangebyscore,zrevrank,zunionstore,xadd,xdel,del,xtrim}
|
||
# Specify which command should be converted to read operation
|
||
plugin.lettuce.operation_mapping_read=${SW_PLUGIN_LETTUCE_OPERATION_MAPPING_READ:getrange,getbit,mget,hvals,hkeys,hlen,hexists,hget,hgetall,hmget,blpop,brpop,lindex,llen,lpop,lrange,rpop,scard,srandmember,spop,sscan,smove,zlexcount,zscore,zscan,zcard,zcount,xget,get,xread,xlen,xrange,xrevrange}
|
||
# If set to true, the parameters of the cypher would be collected.
|
||
plugin.neo4j.trace_cypher_parameters=${SW_PLUGIN_NEO4J_TRACE_CYPHER_PARAMETERS:false}
|
||
# If set to positive number, the `db.cypher.parameters` would be truncated to this length, otherwise it would be completely saved, which may cause performance problem.
|
||
plugin.neo4j.cypher_parameters_max_length=${SW_PLUGIN_NEO4J_CYPHER_PARAMETERS_MAX_LENGTH:512}
|
||
# If set to positive number, the `db.statement` would be truncated to this length, otherwise it would be completely saved, which may cause performance problem.
|
||
plugin.neo4j.cypher_body_max_length=${SW_PLUGIN_NEO4J_CYPHER_BODY_MAX_LENGTH:2048}
|
||
# If set to a positive number and activate `trace sampler CPU policy plugin`, the trace would not be collected when agent process CPU usage percent is greater than `plugin.cpupolicy.sample_cpu_usage_percent_limit`.
|
||
plugin.cpupolicy.sample_cpu_usage_percent_limit=${SW_SAMPLE_CPU_USAGE_PERCENT_LIMIT:-1}
|
||
# This config item controls that whether the Micronaut http client plugin should collect the parameters of the request. Also, activate implicitly in the profiled trace.
|
||
plugin.micronauthttpclient.collect_http_params=${SW_PLUGIN_MICRONAUTHTTPCLIENT_COLLECT_HTTP_PARAMS:false}
|
||
# This config item controls that whether the Micronaut http server plugin should collect the parameters of the request. Also, activate implicitly in the profiled trace.
|
||
plugin.micronauthttpserver.collect_http_params=${SW_PLUGIN_MICRONAUTHTTPSERVER_COLLECT_HTTP_PARAMS:false}
|
||
# Specify which command should be converted to write operation
|
||
plugin.memcached.operation_mapping_write=${SW_PLUGIN_MEMCACHED_OPERATION_MAPPING_WRITE:set,add,replace,append,prepend,cas,delete,touch,incr,decr}
|
||
# Specify which command should be converted to read operation
|
||
plugin.memcached.operation_mapping_read=${SW_PLUGIN_MEMCACHED_OPERATION_MAPPING_READ:get,gets,getAndTouch,getKeys,getKeysWithExpiryCheck,getKeysNoDuplicateCheck}
|
||
# Specify which command should be converted to write operation
|
||
plugin.ehcache.operation_mapping_write=${SW_PLUGIN_EHCACHE_OPERATION_MAPPING_WRITE:tryRemoveImmediately,remove,removeAndReturnElement,removeAll,removeQuiet,removeWithWriter,put,putAll,replace,removeQuiet,removeWithWriter,removeElement,removeAll,putWithWriter,putQuiet,putIfAbsent,putIfAbsent}
|
||
# Specify which command should be converted to read operation
|
||
plugin.ehcache.operation_mapping_read=${SW_PLUGIN_EHCACHE_OPERATION_MAPPING_READ:get,getAll,getQuiet,getKeys,getKeysWithExpiryCheck,getKeysNoDuplicateCheck,releaseRead,tryRead,getWithLoader,getAll,loadAll,getAllWithLoader}
|
||
# Specify which command should be converted to write operation
|
||
plugin.guavacache.operation_mapping_write=${SW_PLUGIN_GUAVACACHE_OPERATION_MAPPING_WRITE:put,putAll,invalidate,invalidateAll,invalidateAll,cleanUp}
|
||
# Specify which command should be converted to read operation
|
||
plugin.guavacache.operation_mapping_read=${SW_PLUGIN_GUAVACACHE_OPERATION_MAPPING_READ:getIfPresent,get,getAllPresent,size}
|
||
# If set to true, the parameters of Redis commands would be collected by Jedis agent.
|
||
plugin.jedis.trace_redis_parameters=${SW_PLUGIN_JEDIS_TRACE_REDIS_PARAMETERS:false}
|
||
# If set to positive number and plugin.jedis.trace_redis_parameters is set to true, Redis command parameters would be collected and truncated to this length.
|
||
plugin.jedis.redis_parameter_max_length=${SW_PLUGIN_JEDIS_REDIS_PARAMETER_MAX_LENGTH:128}
|
||
# Specify which command should be converted to write operation
|
||
plugin.jedis.operation_mapping_write=${SW_PLUGIN_JEDIS_OPERATION_MAPPING_WRITE:getset,set,setbit,setex,setnx,setrange,strlen,mset,msetnx,psetex,incr,incrby,incrbyfloat,decr,decrby,append,hmset,hset,hsetnx,hincrby,hincrbyfloat,hdel,rpoplpush,rpush,rpushx,lpush,lpushx,lrem,ltrim,lset,brpoplpush,linsert,sadd,sdiff,sdiffstore,sinterstore,sismember,srem,sunion,sunionstore,sinter,zadd,zincrby,zinterstore,zrange,zrangebylex,zrangebyscore,zrank,zrem,zremrangebylex,zremrangebyrank,zremrangebyscore,zrevrange,zrevrangebyscore,zrevrank,zunionstore,xadd,xdel,del,xtrim}
|
||
# Specify which command should be converted to read operation
|
||
plugin.jedis.operation_mapping_read=${SW_PLUGIN_JEDIS_OPERATION_MAPPING_READ:getrange,getbit,mget,hvals,hkeys,hlen,hexists,hget,hgetall,hmget,blpop,brpop,lindex,llen,lpop,lrange,rpop,scard,srandmember,spop,sscan,smove,zlexcount,zscore,zscan,zcard,zcount,xget,get,xread,xlen,xrange,xrevrange}
|
||
# If set to true, the parameters of Redis commands would be collected by Redisson agent.
|
||
plugin.redisson.trace_redis_parameters=${SW_PLUGIN_REDISSON_TRACE_REDIS_PARAMETERS:false}
|
||
# If set to positive number and plugin.redisson.trace_redis_parameters is set to true, Redis command parameters would be collected and truncated to this length.
|
||
plugin.redisson.redis_parameter_max_length=${SW_PLUGIN_REDISSON_REDIS_PARAMETER_MAX_LENGTH:128}
|
||
# Specify which command should be converted to write operation
|
||
plugin.redisson.operation_mapping_write=${SW_PLUGIN_REDISSON_OPERATION_MAPPING_WRITE:getset,set,setbit,setex,setnx,setrange,strlen,mset,msetnx,psetex,incr,incrby,incrbyfloat,decr,decrby,append,hmset,hset,hsetnx,hincrby,hincrbyfloat,hdel,rpoplpush,rpush,rpushx,lpush,lpushx,lrem,ltrim,lset,brpoplpush,linsert,sadd,sdiff,sdiffstore,sinterstore,sismember,srem,sunion,sunionstore,sinter,zadd,zincrby,zinterstore,zrange,zrangebylex,zrangebyscore,zrank,zrem,zremrangebylex,zremrangebyrank,zremrangebyscore,zrevrange,zrevrangebyscore,zrevrank,zunionstore,xadd,xdel,del,xtrim}
|
||
# Specify which command should be converted to read operation
|
||
plugin.redisson.operation_mapping_read=${SW_PLUGIN_REDISSON_OPERATION_MAPPING_READ:getrange,getbit,mget,hvals,hkeys,hlen,hexists,hget,hgetall,hmget,blpop,brpop,lindex,llen,lpop,lrange,rpop,scard,srandmember,spop,sscan,smove,zlexcount,zscore,zscan,zcard,zcount,xget,get,xread,xlen,xrange,xrevrange}
|
||
# This config item controls that whether the Netty-http plugin should collect the http body of the request.
|
||
plugin.nettyhttp.collect_request_body=${SW_PLUGIN_NETTYHTTP_COLLECT_REQUEST_BODY:false}
|
||
# When `HTTP_COLLECT_REQUEST_BODY` is enabled, how many characters to keep and send to the OAP backend, use negative values to keep and send the complete body.
|
||
plugin.nettyhttp.filter_length_limit=${SW_PLUGIN_NETTYHTTP_FILTER_LENGTH_LIMIT:1024}
|
||
# When `HTTP_COLLECT_REQUEST_BODY` is enabled and content-type start with HTTP_SUPPORTED_CONTENT_TYPES_PREFIX, collect the body of the request , multiple paths should be separated by `,`
|
||
plugin.nettyhttp.supported_content_types_prefix=${SW_PLUGIN_NETTYHTTP_SUPPORTED_CONTENT_TYPES_PREFIX:application/json,text/}
|
||
# If set to true, the keys of messages would be collected by the plugin for RocketMQ Java client.
|
||
plugin.rocketmqclient.collect_message_keys=${SW_PLUGIN_ROCKETMQCLIENT_COLLECT_MESSAGE_KEYS:false}
|
||
# If set to true, the tags of messages would be collected by the plugin for RocketMQ Java client.
|
||
plugin.rocketmqclient.collect_message_tags=${SW_PLUGIN_ROCKETMQCLIENT_COLLECT_MESSAGE_TAGS:false}
|