Skip to content

Better Documentation, More Logging Options, DB logs storage #48

Description

@jacobg-jellyfish

This is more of a feature request:

This project lacks easy to understand and use documentation and examples.
It would be useful to create documentation that uses more specific examples.

IE: How do you log failed login attempts? With an example.
Or how do you extend the logger, so that you can simply output the logs to std out.

Which brings me to the next point:

Why is this all hosted within the same db as the application? If an attacker were to gain access to the system they could easily cover their tracks. So why is the DB the only place to send logs?

In an enterprise environment one would need to send these logs to either another logging tool or store them else where.

Is this even possibile with the current implementation?

Perhaps some better documentation could help here..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions