# Activity logging using temporal server cli

**URL:** <https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998>\
**Category:** Community Support\
**Tags:** general-impl\
**Created:** [July 24, 2025, 1:22am UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998 "2025-07-24T01:22:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tate\_Jones](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tate_jones/32/5490_2.png) [@Tate\_Jones](https://community.temporal.io/u/Tate_Jones)\
**Post date:** [July 24, 2025, 1:22am UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998/1 "2025-07-24T01:22:59Z")

</div>

During development using the standalone temporal binary I am unable to view any activity logs on the server.

The server is started with:

temporal server start-dev --namespace=development

In an activity using typescript SDK:  
import { log } from “@temporalio/activity”  
…  
log.info(`message!`)

When using temporal within docker this log message is visible on the server.

Thanks in advance  
Tate

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [July 24, 2025, 6:00pm UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998/2 "2025-07-24T18:00:32Z")

</div>

Hi,

> During development using the standalone temporal binary I am unable to view any activity logs on the server.

I guess you mean the workers, the one that run workflow and activity tasks

Can you try adding the logs to this example [samples-typescript/hello-world/src/activities.ts at cc1a3ee2696866f75966b2968ef2291bd5b852f1 · temporalio/samples-typescript · GitHub](https://github.com/temporalio/samples-typescript/blob/cc1a3ee2696866f75966b2968ef2291bd5b852f1/hello-world/src/activities.ts)

It can also be the log configuration , could you review it?

`Runtime.install({ logger:....`

Antonio

---

<div class="post-metadata">

**Author:** ![Tate\_Jones](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tate_jones/32/5490_2.png) [@Tate\_Jones](https://community.temporal.io/u/Tate_Jones)\
**Post date:** [July 24, 2025, 7:54pm UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998/3 "2025-07-24T19:54:19Z")

</div>

I will provide some more code details shortly. But as mentioned the logs do appear when running temporal in a container.

---

<div class="post-metadata">

**Author:** ![Tate\_Jones](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tate_jones/32/5490_2.png) [@Tate\_Jones](https://community.temporal.io/u/Tate_Jones)\
**Post date:** [July 25, 2025, 3:06am UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998/4 "2025-07-25T03:06:08Z")

</div>

The issue was related to the telemetryOptions when the filtering is set to INFO. Even though the messages are at INFO level.

```
filter: makeTelemetryFilterString({ core: 'INFO' }),

```

Nothing appears for activities or workflows. If this toggled to DEBUG the log messages appear.  
If I remove the filter from the telemetryOptions nothing appears.

This is reproducible using the example at:

> **[samples-typescript/custom-logger at main · temporalio/samples-typescript](https://github.com/temporalio/samples-typescript/tree/main/custom-logger)**
>
> Contribute to temporalio/samples-typescript development by creating an account on GitHub.

Change  
filter: makeTelemetryFilterString({ core: 'DEBUG }),  
to  
filter: makeTelemetryFilterString({ core: 'INFO }),

What is the impact to the performance based on this comment in the example?

// This filter determines which logs should be forwarded from Rust Core to the Node.js logger.  
// Note: In production, WARN should generally be enough. DEBUG is quite verbose.

see below…

```auto
  Runtime.install({
    // Install a logger to collect logs generated by Node.js Workers and Rust Core.
    // Note: In production, WARN should generally be enough. DEBUG is quite verbose.
    logger: new DefaultLogger('INFO', (entry) => {
      winstonLogger.log({
        label: entry.meta?.activityId ? 'activity' : entry.meta?.workflowId ? 'workflow' : 'worker',
        level: entry.level.toLowerCase(),
        message: entry.message,
        timestamp: Number(entry.timestampNanos / 1_000_000n),
        ...entry.meta,
      });
    }),
    // Telemetry options control how logs are exported out of Rust Core.
    telemetryOptions: {
      logging: {
        // By default, Core logs go directly to console. Setting the `forward` property here (to an
        // empty object) enables forwarding of logs from Rust Core to the Node.js logger.
        forward: {},
        // This filter determines which logs should be forwarded from Rust Core to the Node.js logger.
        // Note: In production, WARN should generally be enough. DEBUG is quite verbose.
        filter: makeTelemetryFilterString({ core: 'INFO' }),
      },
    },
  });

```

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [July 29, 2025, 1:29pm UTC](https://community.temporal.io/t/activity-logging-using-temporal-server-cli/17998/5 "2025-07-29T13:29:50Z")

</div>

I see, thanks for the clarification,

would you open an issue [GitHub - temporalio/sdk-typescript: Temporal TypeScript SDK](https://github.com/temporalio/sdk-typescript) ?

Antonio