stackabletech / stackabletech/superset-operator

Make tracing in python-ldap configurable

Open
#365 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
35
Forks
4
Avg merge
12h 20m
Merged PRs (30d)
10

Description

Description

Currently there is no logging available to debug LDAP problems. The python-ldap library seems to have a way to turn tracing on but this is different than the usual Python logging infra.

Ideally, setting the log level to trace/debug would also enable LDAP traffic tracing.

This might need patching the flask app builder.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining how python-ldap tracing and the Flask App Builder logging configuration work together. Confirm whether the integration exposes LDAP traffic tracing through the usual log levels; done means enabling trace/debug logging also enables LDAP tracing without a separate mechanism.

Written by the indexing model from the issue text.

Assessment

Tech stack
flask, python
Domain
backend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.