Skip to content

Conversation

@asergunov
Copy link
Contributor

Description

Using structured logger to improve performance by reducing string allocations

Why do we need it, and what problem does it solve?

That was planned long ago. Now it's done.

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Updated the logging mechanism in the getBlockDeviceCandidates function to use a structured logger with contextual information. This change enhances log readability and traceability by including device-specific details in log messages.

Signed-off-by: Anton Sergunov <[email protected]>
Signed-off-by: Anton Sergunov <[email protected]>
@asergunov asergunov self-assigned this Nov 13, 2025
@asergunov asergunov added the enhancement New feature or request label Nov 13, 2025
…d device labels for better traceability. This update improves the context of log messages when a block device does not match the specified labels.

Signed-off-by: Anton Sergunov <[email protected]>
…improved logging functionality.

Signed-off-by: Anton Sergunov <[email protected]>
…vels

Updated the logger methods to remove string formatting and include log levels as structured fields. This change enhances log clarity and consistency across the logger implementation.

Signed-off-by: Anton Sergunov <[email protected]>
…WARNING" for improved log accuracy.

Signed-off-by: Anton Sergunov <[email protected]>
… formatting for improved clarity.

Signed-off-by: Anton Sergunov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants