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

KERIA logs should indicate the agent that the log applies to #324

Open
2byrds opened this issue Nov 21, 2024 · 4 comments
Open

KERIA logs should indicate the agent that the log applies to #324

2byrds opened this issue Nov 21, 2024 · 4 comments

Comments

@2byrds
Copy link
Collaborator

2byrds commented Nov 21, 2024

Feature request description/rationale

Currently there is no distinction between logs per agent. Perfix the logs with the agent id.

@lenkan
Copy link
Collaborator

lenkan commented Nov 27, 2024

It would be useful if the log format was standardized throughout as well. Maybe to take inspiration from https://en.wikipedia.org/wiki/Common_Log_Format.

If we add the controller id and/or agent id, and then log every request, it would be much easier to track down certain errors.

@2byrds
Copy link
Collaborator Author

2byrds commented Dec 3, 2024

From our dev meeting, the keri logging has advanced log features to add additional fields, for instance different formatters. There might be some witness examples with formatters.

@2byrds
Copy link
Collaborator Author

2byrds commented Dec 3, 2024

Look in keripy help.tests.help.oggler class definition for examples. There is some hio compatible logger stuff. you can change the f-strings. Phil showed the example:
image
It is recommended to put the agent information in a f-string
The log module source is through hio, but keri import should be from help.

@2byrds
Copy link
Collaborator Author

2byrds commented Dec 3, 2024

From Sam during the meeting:
"ogler = ogling.initOgler(prefix='keri', syslogged=False) # inits once only on first import
This is in keri.help.init.py
so import ogler from keri.help to get prefix of 'keri'
To get a module specific prefix then import ogling from keri.help and then create a module specific ogler with a different prefix.
The reason not to import ogler from hio is so that any keri specific configuration can happen in keri.help and all keri submodules inherit that behavior."

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

No branches or pull requests

2 participants