method TracingChannel.prototype.traceSync
Unstable
Usage in Deno
```typescript import { TracingChannel } from "node:node__diagnostics_channel.d.ts"; ```
TracingChannel.prototype.traceSync<ThisArg = any,Args extends any[] = any[],>(fn: (this: ThisArg,...args: Args,) => any,context?: ContextType,thisArg?: ThisArg,...args: Args,): void
Trace a synchronous function call. This will always produce a `start event` and `end event` around the execution and may produce an `error event` if the given function throws an error.
This will run the given function using `channel.runStores(context, ...)` on the `start` channel which ensures all
events should have any bound stores set to match this trace context.
To ensure only correct trace graphs are formed, events will only be published if subscribers are present prior to starting the trace. Subscriptions
which are added after the trace begins will not receive future events from that trace, only future traces will be seen.
```js
import diagnostics_channel from 'node:diagnostics_channel';
const channels = diagnostics_channel.tracingChannel('my-channel');
channels.traceSync(() => {
// Do something
}, {
some: 'thing',
});
```
void
The return value of the given function