table of contents
- unstable 0.8.14-5.1
md_src_plugins_tracer_README - README
- infos = Information about the tracer plugin is in keys below
- infos/author = Markus Raab firstname.lastname@example.org
- infos/licence = BSD
- infos/needs =
- infos/provides = logging
- infos/placements = pregetstorage postgetstorage presetstorage precommit postcommit prerollback postrollback
- infos/description = Traces the execution path of a backend
This plugin is added on every possible position within a backend. It allows you to trace when the backend is executed.
If you want to trace how and if the backend is called:
kdb mount file.ysp user/trace_point your_storage_plugin tracer
So now we can trace whats below your trace point.
kdb ls user/trace_point
Ok, no tracer is called because resolver immediately told that there is no file.
kdb get user/trace_point Did not find key
Ok, same conclusion.
kdb set user/trace_point hello create a new key user/trace_point with string hello tracer: set(0xd34cc0, user/trace_point): user/trace_point 1 tracer: set(0xd34cc0, user/trace_point): user/trace_point 1 tracer: set(0xd34cc0, user/trace_point): user/trace_point 1
Now the 3 placements in set are called.
kdb get user/trace_point tracer: get(0x22e1cc0, user/trace_point): 0 tracer: get(0x22e1cc0, user/trace_point): 0 hello
Now the 2 placements in get are called.
|Sun May 29 2016||Version 0.8.14|