logging-objects-with-schema 0.1.0__tar.gz

logging_objects_with_schema-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Dmitrii Safronov
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

logging_objects_with_schema-0.1.0/PKG-INFO

@@ -0,0 +1,440 @@
+Metadata-Version: 2.4
+Name: logging-objects-with-schema
+Version: 0.1.0
+Summary: Proxy logging wrapper that validates extra fields against a JSON schema.
+Keywords: logging,schema,validation,structured-logging,structured-logs
+Author: Dmitrii Safronov
+Author-email: Dmitrii Safronov <dhameoelin+logging-objects-with-schema@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: System :: Logging
+Requires-Dist: pytest>=7.0.0 ; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0.0 ; extra == 'dev'
+Requires-Dist: black>=23.0.0 ; extra == 'dev'
+Requires-Dist: isort>=5.12.0 ; extra == 'dev'
+Requires-Dist: flake8>=6.0.0 ; extra == 'dev'
+Requires-Dist: flake8-pyproject>=1.2.3 ; extra == 'dev'
+Requires-Dist: mypy>=1.18.1 ; extra == 'dev'
+Requires-Dist: bandit>=1.8.6 ; extra == 'dev'
+Requires-Dist: pre-commit>=3.5.0 ; extra == 'dev'
+Requires-Python: >=3.10
+Project-URL: Issues, https://github.com/disafronov/python-logging-objects-with-schema/issues
+Project-URL: Source, https://github.com/disafronov/python-logging-objects-with-schema
+Provides-Extra: dev
+Description-Content-Type: text/markdown
+
+# python-logging-objects-with-schema
+
+This library provides a logger subclass built on top of the standard `logging`
+module that strictly controls additional `extra` fields using a JSON schema.
+
+## Core idea
+
+- The standard `logging` package is used (your application configures handlers
+  and formatting as usual).
+- `SchemaLogger` is a subclass of `logging.Logger` designed to be used as a
+  drop-in replacement via `logging.setLoggerClass(SchemaLogger)`.
+- The schema is stored in a JSON file named `logging_objects_with_schema.json`
+  in the application root directory.
+- Any user-provided `extra` fields are included in the log **only if** they are
+  described in the schema and match the declared Python type.
+- The library is universal and works with any formatters from the standard
+  `logging` module. It is not tied to any specific log format or logging library.
+
+## Schema as a contract
+
+The JSON schema is treated as a **contract** between all parties that produce
+and consume logs in the system. It defines which structured fields are allowed
+to appear in logs and which types they must have.
+
+- Application code must only send `extra` fields that are described in the schema
+  and match the declared Python types. Any deviation (unknown fields, wrong types,
+  `None` values, disallowed list elements) is reported via `DataValidationError`
+  *after* the log record has been emitted.
+- The schema file (`logging_objects_with_schema.json`) is a shared, versioned
+  artifact that defines the shape of structured log payloads for all downstream
+  consumers (search, alerts, dashboards, external systems).
+
+## Strictness guarantees
+
+- Only fields explicitly described in the JSON schema (as leaves with `type` and
+  `source`) can ever reach your logs.
+- Any `extra` field that is **not** described in the schema is treated as a data
+  error: it is dropped from the log output and recorded as a validation problem.
+- Any mismatch between runtime values and the declared types is also treated as
+  a data error.
+- All validation problems (unknown fields, wrong types, disallowed list
+  elements, `None` values, etc.) are aggregated into a single
+  `DataValidationError` that is raised **after** the log record has been
+  emitted.
+- The schema is treated as the only source of truth for which `extra` fields
+  are allowed to appear in logs. Any deviation from the schema is considered a
+  contract violation between the producer of `extra` and the schema author.
+
+## Installation
+
+```bash
+pip install logging-objects-with-schema
+```
+
+## Basic usage
+
+### Quickstart (complete working example)
+
+First, create a schema file `logging_objects_with_schema.json` in your application root:
+
+```json
+{
+  "ServicePayload": {
+    "RequestID": {"type": "str", "source": "request_id"},
+    "UserID": {"type": "int", "source": "user_id"}
+  }
+}
+```
+
+Then, set up and use the logger:
+
+```python
+import logging
+import sys
+
+from logging_objects_with_schema import SchemaLogger
+
+
+# Set SchemaLogger as the default logger class
+logging.setLoggerClass(SchemaLogger)
+
+# Configure handlers and formatters as usual
+handler = logging.StreamHandler(sys.stdout)
+handler.setFormatter(logging.Formatter("%(message)s %(ServicePayload)s"))
+
+# Get loggers using standard logging API
+logger = logging.getLogger("service")
+logger.setLevel(logging.INFO)
+logger.addHandler(handler)
+
+# Use the logger - extra fields are validated against the schema
+logger.info("request processed", extra={"request_id": "abc-123", "user_id": 42})
+```
+
+### Example with nested structures
+
+Schema with nested structure:
+
+```json
+{
+  "ServicePayload": {
+    "RequestID": {"type": "str", "source": "request_id"},
+    "UserID": {"type": "int", "source": "user_id"},
+    "Metrics": {
+      "CPU": {"type": "float", "source": "cpu_usage"},
+      "Memory": {"type": "float", "source": "memory_usage"},
+      "Network": {
+        "In": {"type": "int", "source": "network_in"},
+        "Out": {"type": "int", "source": "network_out"}
+      }
+    }
+  }
+}
+```
+
+Usage:
+
+```python
+logger.info(
+    "metrics collected",
+    extra={
+        "request_id": "req-123",
+        "user_id": 42,
+        "cpu_usage": 75.5,
+        "memory_usage": 60.2,
+        "network_in": 1024,
+        "network_out": 2048,
+    }
+)
+```
+
+### Error handling example
+
+```python
+from logging_objects_with_schema import SchemaLogger, DataValidationError, SchemaValidationError
+
+try:
+    # This will raise SchemaValidationError if schema file is missing or invalid
+    logging.setLoggerClass(SchemaLogger)
+    logger = logging.getLogger("service")
+except SchemaValidationError as e:
+    print(f"Schema validation failed: {e}")
+    for problem in e.problems:
+        print(f"  - {problem.message}")
+    # Decide whether to abort or continue with default logger
+    raise
+
+# When logging, handle DataValidationError
+try:
+    logger.info("processing", extra={"user_id": "not-an-int"})  # Wrong type
+except DataValidationError as e:
+    print(f"Data validation failed: {e}")
+    for problem in e.problems:
+        print(f"  - {problem.message}")
+    # Note: the valid part of the log was already emitted before the exception
+```
+
+### API compatibility with ``logging.Logger``
+
+- ``SchemaLogger`` is a subclass of ``logging.Logger`` and can be used as a
+  drop-in replacement via ``logging.setLoggerClass(SchemaLogger)``.
+- The public methods of ``SchemaLogger`` mirror the standard ``logging.Logger``
+  API and accept the same arguments: ``msg, *args, **kwargs``.
+- The only behavioural difference is that the named ``extra`` argument is
+  intercepted, validated according to the JSON schema, and only the validated
+  subset is passed further into the standard logging pipeline.
+
+## Schema location and format
+
+- Schema file: `logging_objects_with_schema.json`.
+- Location: **application root directory**. The library searches upward from the
+  current working directory for the schema file itself, walking up the directory
+  tree until it finds the file or reaches the filesystem root.
+- Schema tree depth is limited to a maximum nesting level (currently 100). Any
+  branch that exceeds this depth is ignored and reported as a schema problem.
+
+  If the schema file is not found, or cannot be read/parsed/validated, a
+  `SchemaValidationError("Schema has problems", problems=[...])` is raised when
+  a `SchemaLogger` instance is created. In this case the logger instance is not
+  created at all. The `problems` list contains a detailed description of the
+  issue, including the path where the file was expected (based on the current
+  working directory at schema discovery time).
+
+An example schema:
+
+```json
+{
+  "ServicePayload": {
+    "RequestID": {"type": "str", "source": "request_id"},
+    "UserID": {"type": "int", "source": "user_id"},
+    "Metrics": {
+      "CPU": {"type": "float", "source": "cpu_usage"},
+      "Memory": {"type": "float", "source": "memory_usage"},
+      "Network": {
+        "In": {"type": "int", "source": "network_in"},
+        "Out": {"type": "int", "source": "network_out"}
+      }
+    }
+  }
+}
+```
+
+- An inner node is an object without `type` and `source`.
+- A leaf node is an object with both `type` and `source`.
+- `type` is one of the allowed Python type names: `"str"`, `"int"`, `"float"`,
+  `"bool"`, or `"list"`.
+- For `"list"` type, an additional `item_type` field is required to declare
+  the element type. Only primitive element types (`"str"`, `"int"`, `"float"`,
+  `"bool"`) are allowed. Nested lists and dictionaries are not permitted as
+  list elements.
+- `source` is the name of the field in `extra` from which the value is taken.
+
+### List-typed fields
+
+When a leaf declares `"type": "list"`, the runtime value must be a Python list
+with **homogeneous primitive elements**. The element type is defined by the
+mandatory `item_type` field:
+
+- Allowed `item_type` values: `"str"`, `"int"`, `"float"`, `"bool"`
+- All elements in the list must have exactly the declared Python type
+  (e.g. `type(item) is int` for `"item_type": "int"`)
+- Empty lists are allowed
+- Nested lists and dictionaries inside the list are not allowed
+
+Example of a valid list field:
+
+```json
+{
+  "ServicePayload": {
+    "Tags": {
+      "type": "list",
+      "source": "tags",
+      "item_type": "str"
+    }
+  }
+}
+```
+
+Usage:
+
+```python
+logger.info(
+    "request processed",
+    extra={
+        "tags": ["blue", "fast", "cached"],  # list[str] – valid
+    },
+)
+```
+
+Example of an invalid list field (non-primitive elements):
+
+```python
+logger.info(
+    "request processed",
+    extra={
+        "tags": [{"key": "color", "value": "blue"}],  # list[dict] – invalid
+    },
+)
+```
+
+In this case the `tags` value is rejected, a `DataProblem` is recorded with a
+message similar to:
+
+> Field 'tags' is a list but contains elements with types [...]; expected all elements to be of type str
+
+and a `DataValidationError` is raised **after** the log record has been emitted.
+
+### Multiple leaves with the same source
+
+A single `source` field name can be used in multiple leaves of the schema. This
+allows the same value from `extra` to be placed in different locations of the
+output structure.
+
+When a `source` is referenced by multiple leaves:
+
+- The value is validated against each leaf's expected type independently.
+- The value is written only to those leaf locations where the runtime type
+  matches the expected type.
+- For leaf locations where the type does not match, a `DataProblem` is added
+  to the `DataValidationError` that is raised after logging.
+
+Example schema with duplicate source usage:
+
+```json
+{
+  "ServicePayload": {
+    "RequestID": {"type": "str", "source": "request_id"},
+    "Metadata": {
+      "ID": {"type": "str", "source": "request_id"}
+    }
+  }
+}
+```
+
+In this example, if `extra={"request_id": "abc-123"}`, the value `"abc-123"`
+will be written to both `ServicePayload.RequestID` and `ServicePayload.Metadata.ID`.
+
+If the same `source` is used with conflicting types (e.g., one leaf expects
+`str` and another expects `int`), the value will only be written to locations
+where the type matches, and validation problems will be reported for the
+mismatched locations. It is the schema author's responsibility to ensure
+consistent type expectations when reusing a `source` field.
+
+## Behaviour when loading the schema
+
+- When a `SchemaLogger` instance is created (via `logging.getLogger()` after
+  `logging.setLoggerClass(SchemaLogger)`), the library:
+  - searches for `logging_objects_with_schema.json` by walking upward from
+    the current working directory until it finds the file or reaches the
+    filesystem root;
+  - parses the JSON;
+  - walks the entire tree and collects all problems with the schema.
+- If there are **any** problems with the schema (missing file, broken JSON,
+  invalid `type` values, conflicting root fields that match system logging
+  fields, malformed structure, etc.):
+  - a `SchemaValidationError("Schema has problems", problems=[...])` is raised;
+  - the logger instance is not created.
+- If there are no problems:
+  - the schema is compiled into a `CompiledSchema`;
+  - the logger is created and starts using this schema to validate `extra`
+    fields.
+
+The application decides whether `SchemaValidationError` is a fatal error that
+should abort startup, or whether it should be logged and ignored.
+
+## Schema caching and thread safety
+
+- The library caches compiled schemas to avoid recompiling the same schema file
+  on every logger creation.
+- The cache is keyed by the absolute schema file path and stores both the
+  compiled schema and any discovered problems. Once a schema (or its absence /
+  invalidity) has been observed for a given path, subsequent calls reuse the
+  cached result within the same process without re-reading or re-compiling the
+  schema file.
+- This includes invalid schemas: once a schema file has been found to be
+  invalid, the corresponding (typically empty) `CompiledSchema` and its
+  `SchemaProblem`s are reused for the lifetime of the process.
+- Schema compilation and cache access are **thread-safe**: multiple threads can
+  safely create `SchemaLogger` instances concurrently without race conditions.
+- The schema is effectively loaded and compiled **once per process** for a
+  given schema path. Subsequent logger instances reuse the cached compiled
+  schema.
+- **Note**: The library does not provide a mechanism to reload the schema
+  without restarting the application. This is a deliberate design decision to
+  ensure schema consistency throughout the application lifecycle.
+
+## Schema root key restrictions
+
+- The library protects system fields from the standard `logging` module
+  (attributes of `LogRecord` and logger internals) by preventing their use as
+  root keys in the schema.
+- If a root key in the schema conflicts with a system logging field, a
+  `SchemaProblem` is generated and the schema validation fails.
+- Responsibility for ensuring compatibility with other logging libraries and
+  formatters lies with the developer when writing the schema.
+
+## Behaviour when logging data
+
+- Any `extra` provided by the application **never goes directly** into the log.
+- The only way for additional fields to reach the log:
+  1. The field is described as a leaf in the schema (`type` + `source`).
+  2. `extra` contains a value under the given `source` name.
+  3. The runtime type of the value strictly matches the declared Python type
+     (exact type match is used, e.g. `bool` is not accepted where `int` is
+     expected, and vice versa).
+- If:
+  - the compiled schema has no valid leaves (it is effectively empty, so no
+    `extra` keys are ever allowed to contribute data);
+  - a field is not described in the schema;
+  - the type does not match the declared type;
+  - the value is None (None values are not allowed);
+  - the field is considered redundant,
+  **it is simply not included in the final log record**.
+
+In all of these cases a `DataProblem` is recorded for each offending field, and
+if at least one problem is present a single `DataValidationError` is raised
+**after** the log record has been emitted.
+
+- When a `source` is used in multiple leaves (see "Multiple leaves with the same
+  source" above), the value is validated and written independently for each leaf
+  location.
+- Before emitting the final structured payload, the library strips empty
+  dictionaries and `None` values from nested structures so that only meaningful
+  data appears in the resulting log record.
+
+High-level algorithm inside `SchemaLogger`:
+
+- For every call to `logger.info` / `logger.error` / `logger.log`:
+  1. All user-provided fields are taken from `extra`.
+  2. A new structured payload is built from the schema and the given `extra`.
+  3. Only this structured payload is passed to the underlying stdlib logger.
+  4. After logging, if any validation problems were detected, a single
+     `DataValidationError` is raised with the full `problems` list.
+
+## Exceptions
+
+- **`SchemaValidationError`**:
+  - Any problem with the schema (missing file, broken JSON, invalid types,
+    conflicting root fields, malformed structure, etc.).
+  - Exposes a `problems` list describing each violation.
+- **`DataValidationError`**:
+  - Any problem with a specific `extra` payload during logging:
+    - the runtime type does not match the expected type;
+    - a list contains non-primitive elements (only str, int, float, bool allowed);
+    - the field is redundant and not described in the schema.
+  - Raised **after** the valid part of the payload has been logged.
+  - Contains a `problems` list describing the offending fields.