Skip to content

Add logging documentation for Python SDK generator#3671

Closed
iamnamananand996 wants to merge 2 commits into
mainfrom
devin/1771413179-python-logging-docs
Closed

Add logging documentation for Python SDK generator#3671
iamnamananand996 wants to merge 2 commits into
mainfrom
devin/1771413179-python-logging-docs

Conversation

@iamnamananand996
Copy link
Copy Markdown
Contributor

Add logging documentation for Python SDK generator

Summary

Adds a new docs page documenting the configurable logging system introduced in the Python SDK generator (via fern-api/fern#12219). The page covers basic LogConfig usage, pre-configured Logger instances, custom ILogger implementations, a table of what gets logged, and a configuration reference using <ParamField> components.

The page is registered in the Python section of the SDK sidebar navigation, between "Dynamic authentication" and the changelog.

Review & Testing Checklist for Human

  • Verify ConsoleLogger and ILogger are actually exported from generated SDKs. The code examples import these from my_sdk.core, but the implementation PR (#12219) may have only added LogConfig, LogLevel, Logger, and create_logger to the generated core/__init__.py dynamic imports. If these symbols aren't exported, the "pre-configured Logger instance" example will mislead users. This is the highest priority item.
  • Preview the rendered page in the Fern docs site to confirm the MDX renders correctly — particularly the <ParamField> components, <Note> callout, and the markdown table.
  • Check that the page URL (/learn/sdks/generators/python/logging) doesn't conflict with any existing redirects in docs.yml.

Notes

  • The code examples use token="YOUR_TOKEN" as a generic auth placeholder. Actual generated SDKs may use different parameter names depending on auth configuration.
  • This PR does not add logging docs for TypeScript or other generators — only Python, which is the language that just received the logging feature.

Link to Devin run: https://app.devin.ai/sessions/416c0ce2bffb4596aa37a8563fd7076b
Requested by: @iamnamananand996

Co-Authored-By: naman.anand@buildwithfern.com <iamnamananand996@gmail.com>
@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

| Error response (4xx/5xx) | `error` | Method, URL, status code, redacted response headers |

<Note>
Sensitive headers such as `Authorization`, `Cookie`, `X-API-Key`, and `X-CSRF-Token` are automatically replaced with `[REDACTED]` in all log output. This prevents accidental leakage of credentials in logs.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[FernStyles.Acronyms] 'CSRF' has no definition.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 18, 2026

🌿 Preview your docs: https://fern-preview-db08f451-87eb-4c74-897b-4259bab5da57.docs.buildwithfern.com/learn

Here are the markdown pages you've updated:

Co-Authored-By: naman.anand@buildwithfern.com <iamnamananand996@gmail.com>
| Error response (4xx/5xx) | `error` | Method, URL, status code, redacted response headers |

<Note>
Sensitive headers such as `Authorization`, `Cookie`, `X-API-Key`, and `X-CSRF-Token` (Cross-Site Request Forgery) are automatically replaced with `[REDACTED]` in all log output. This prevents accidental leakage of credentials in logs.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[FernStyles.Acronyms] 'CSRF' has no definition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant