You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should see the bound_key and second_key values in the logs. bound_key should be present for both statements. second_key should be present for just the first statement.
Acceptance criteria
Above scenario is implemented and works with vdk-structlog
The text was updated successfully, but these errors were encountered:
## Why?
As part of VEP-2448, we'd like to make structured logging pluggable
## What?
Create a vdk-structlog plugin. The plugin allows users to configure
logging metadata and logging format. It also works with bound loggers.
## How was this tested?
Installed the plugin and ran a data job locally with different
configurations
## White kind of change is this?
feature/non-breaking
## Follow-up
- #2802
- #2803
- #2810
- #2811
- #2812
- #2813
- #2814
Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
Overview
Vdk users should have the option of binding additional context to their log statements. This should be provided out of the box by vdk-core.
Example:
Somewhere else in core, plugin or data job code
Then, with vdk-structlog installed and a metadata config like
We should see the bound_key and second_key values in the logs. bound_key should be present for both statements. second_key should be present for just the first statement.
Acceptance criteria
The text was updated successfully, but these errors were encountered: