Skip to content

[Feature Request]: Improve internal logging functionality #1955

Open
@jgbradley1

Description

@jgbradley1

Do you need to file an issue?

  • I have searched the existing issues and this feature is not already filed.
  • My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
  • I believe this is a legitimate feature request, not just a question. If this is a question, please use the Discussions area.

Is your feature request related to a problem? Please describe.

The current logging mechanisms implemented in the graphrag python package are complicated and do not conform to best-practice standards. It is difficult to capture all log messages from the graphrag library in a consistent manner.

Describe the solution you'd like

The custom logging functionality inside the graphrag package should be refactored and swapped out for the built-in Python logging module. Please use standard best-practices when utilizing the logging module.

Additional context

How to use the Python logging module is described in the following article:

https://betterstack.com/community/guides/logging/how-to-start-logging-with-python

Use that article as the basis for best-practices for Python logging.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions