Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLI-769] Allow for debug logging in engine #60

Open
markphelps opened this issue Jan 2, 2024 · 0 comments
Open

[FLI-769] Allow for debug logging in engine #60

markphelps opened this issue Jan 2, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed linear Created by Linear-GitHub Sync

Comments

@markphelps
Copy link
Contributor

markphelps commented Jan 2, 2024

We need a way to enable debug level logging for the engine, for example to see:

  • what namespaces/flags the engine is aware of
  • the results of requests to Flipt server
  • the results of evaluation for variant/boolean

I think this will need to be implemented in two parts:

  1. Add debug logging to the rust engine guarded
  2. Add a way to configure this logging level per each client and pass that down to the rust engine

Instead of simply enabling DEBUG or not, we could think about how to support X number of log levels, like DEBUG, INFO, WARN, ERROR for example and standardize on those

FLI-769

@markphelps markphelps added enhancement New feature or request help wanted Extra attention is needed linear Created by Linear-GitHub Sync and removed linear Created by Linear-GitHub Sync labels Jan 13, 2024
@markphelps markphelps changed the title Allow for debug logging in engine [FLI-769] Allow for debug logging in engine Jan 15, 2024
@markphelps markphelps added this to the Client Evaluation milestone Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed linear Created by Linear-GitHub Sync
Projects
Status: No status
Development

No branches or pull requests

1 participant