[
https://issues.apache.org/jira/browse/IGNITE-23160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-23160:
---------------------------------------
Description:
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.finish()
{noformat}
Possible implementation options:
# OpenTracing API based intergration
# Event based tracing
## lttng for Linux
## JFR
# Trace logging (simplest approach with most overhead)
Clarification is required.
was:
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 implementation options:
# OpenTracing API based intergration
# Event based tracing
## lttng for Linux
## JFR
# Trace logging (simplest approach with most overhead)
Clarification is required.
> Implement tracing capability
> ----------------------------
>
> Key: IGNITE-23160
> URL: https://issues.apache.org/jira/browse/IGNITE-23160
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> 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.finish()
> {noformat}
> Possible implementation 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)
