You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2024/09/06 10:03:00 UTC
[jira] [Created] (IGNITE-23160) Implement tracing capability
Alexey Scherbakov created IGNITE-23160:
------------------------------------------
Summary: Implement tracing capability
Key: IGNITE-23160
URL: https://issues.apache.org/jira/browse/IGNITE-23160
Project: Ignite
Issue Type: Improvement
Reporter: Alexey Scherbakov
We need a way to trace certain server side operations (for example upsert) to address possible performance issues in the fields.
General approach is to mark the code with tracing entries:
{noformat}
Event event = create("someOperation", traceId, label, ...);
event.begin()
...
event.end()
{noformat}
Possible options:
# OpenTracing API based intergration
# Event based tracing
## lttng for Linux
## JFR
# Trace logging (simplest approach with most overhead)
Clarification is required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)