Activity Logs package feedback request

Dear Elm Community,

I hope this message finds you well. I am writing to receive feedback on the elm-activity-logs package, a tool for managing activity logs in Elm applications.

However, after using the elm-activity-logs package locally, I believe there is a significant opportunity for improvement. Currently, the package does not offer a built-in mechanism for saving logs into a text or JSON file. As logs are essential for auditing, debugging, and generating reports, it would be highly beneficial to include this feature within the package.

I would like to propose the inclusion of a log saving feature within the elm-activity-logs package. This feature could include options to save logs as text or JSON files, with the ability to specify a preferred file format, file path, and log rotation options.

Additionally, it would be advantageous to incorporate configurable log levels, allowing developers to filter logs based on their severity or importance. This would further enhance the package’s flexibility and usability.

I believe that integrating log saving functionality into the elm-activity-logs package would greatly benefit the Elm community. It would streamline the process of managing activity logs and provide developers with a comprehensive solution for tracking, storing, and analyzing log data.

I genuinely appreciate your dedication to enhancing Elm’s ecosystem and look forward to the potential growth and improvement of the elm-activity-logs package. Please post your feedback and comments on the package.

Thank You.

I don’t use the current version, but it definitely seems like it could be useful. How would saving work in a web context? Would it a download link or something like that?

I’m attempting to create a function(s) that can automatically save logs within a module. Currently, I’m utilizing the elm/json and elm/file ways.

The goal is to enable the logging of any function within any module, storing the logs in a JSON file. For instance, in an example involving increment and decrement operations, a JSON file would be generated. Each time a user clicks either button, the activity would be recorded in the logs.

I would greatly appreciate any insights or suggestions from the community regarding this matter.

I guess my question was that there is no access to the file system from the browser, so I was wondering what was going to happen to the file. I haven’t used this, so I’m probably not the best person to ask, but it seems like writing the logs to an api endpoint might be more useful in production, although have logs might help debugging locally?

1 Like

I think, dubugging in elm is in a very good status as of now, but yeah, it can be used if one wants it to.

The api endpoint makes sense, thank you for the hint.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.