logo
search
Back to Pixie
COLLAPSE ALL
  • Home
  • About Pixie
    • Pixie Overview
    • Data Sources
    • How Pixie uses eBPF
    • Roadmap
    • FAQ
    • Troubleshooting
  • Installing Pixie
    • Requirements
  • Using Pixie
    • Using the Live UI
    • Using the CLI
    • Using the API
  • Tutorials
    • Index
  • Reference
    • Architecture
    • Data Tables
      • amqp_events
      • conn_stats
      • cql_events
      • dns_events
      • http_events
      • jvm_stats
      • kafka_events.beta
      • mux_events
      • mysql_events
      • nats_events.beta
      • network_stats
      • pgsql_events
      • probe_status
      • proc_exit_events
      • process_stats
      • redis_events
      • stack_traces.beta
      • stirling_error
WebsiteSlack Us
Ver. n/a

stack_traces.beta

Sampled stack traces of applications that identify hot-spots in application code. Executable symbols are required for human-readable function names to be displayed.

ColumnTypePatternDesc
time_TIME64NSMETRIC_COUNTERTimestamp when the data record was collected.
upidUINT128GENERALAn opaque numeric ID that globally identify a running process inside the cluster.
stack_trace_idINT64GENERALA unique identifier of the stack trace, for script-writing convenience. String representation is in the `stack_trace` column.
stack_traceSTRINGGENERALA stack trace within the sampled process, in folded format. The call stack symbols are separated by semicolons. If symbols cannot be resolved, addresses are populated instead.
countINT64METRIC_GAUGENumber of times the stack trace has been sampled.
This site uses cookies to provide you with a better user experience. By using Pixie, you consent to our use of cookies.