# "Activity error" log context keys for structured logging

**URL:** <https://community.temporal.io/t/activity-error-log-context-keys-for-structured-logging/10140>\
**Category:** Community Support\
**Tags:** go-sdk\
**Created:** [November 17, 2023, 5:42pm UTC](https://community.temporal.io/t/activity-error-log-context-keys-for-structured-logging/10140 "2023-11-17T17:42:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![TJ\_White](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tj_white/32/4561_2.png) [@TJ\_White](https://community.temporal.io/u/TJ_White)\
**Post date:** [November 17, 2023, 5:42pm UTC](https://community.temporal.io/t/activity-error-log-context-keys-for-structured-logging/10140/1 "2023-11-17T17:42:20Z")

</div>

Hi team, I am using the golang SDK and I am seeing some logs being produced by the SDK I have a few questions about. When an activity fails, we see this error produced by the sdk “Activity error”.

In other logs from the SDK, WorkflowType is usually set, is there a reason this is missing? Is this something we can add as a feature request? This would help our teams who manage multiple workflows split between workflow types for metrics / triaging errors.

Is there a way to inject context variables into this via a With(…) call? I’d like to inject some application specific IDs so that we can track which internal entities have such errors and possibly retry / replay the workflow if retries don’t end up fixing it.

```auto
{
    "Level": "error",
    "timestamp": "2023-11-15T17:51:47.569Z",
    "Caller": "internal/internal_task_handlers.go:2101",
    "Event": "Activity error.",
    "Namespace": "default",
    "TaskQueue": "redacted",
    "WorkerID": "redacted",
    "WorkflowID": "c105392d-340d-47ce-9aa2-65d253463722",
    "RunID": "5aa027d2-2194-4d6e-8509-474ce664e215",
    "ActivityType": "redacted",
    "Attempt": 4,
    "Error": "redacted",
    "ErrorVerbose": "redacted",
    "Stacktrace": "redacted"
}

```