-
Notifications
You must be signed in to change notification settings - Fork 329
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
Individual loggers for each ChargePoint instance #655
Comments
I think this requirement that I am facing could be a part of a bigger feature where the |
@OrangeTux, is the repo still maintained? |
@OrangeTux @Jared-Newell-Mobility @proelke, let us know if the library is still being maintained. |
You're right. This library isn't really maintained anymore. |
@mdwcrft You have expressed interest to take over ownership of this project. Is that offer still up? |
@OrangeTux , I am also willing to contribute and keep this library up to date. |
Hey @OrangeTux, any chance I can get the opportunity to maintain this package? |
@OrangeTux @Jared-Newell-Mobility @proelke, let me know if I can help you manage this package. |
Hello @jainmohit2001, thanks for your offer. Ideally, I'm looking for multiple people to take over ownership, so I'll announce publicly that this project looking for new owners. |
Yep I'm happy to be added as a maintainer if there are others to make up for my rusty Python! |
I wanted to let you know that I implemented this feature and submitted a pull request about four months ago: #641 The pull request is still awaiting review. |
Duplicate of #641 |
Hi there.
I have been using the library for quite a while now.
I have recently come up with a small requirement: I want to log the OCPP stream to AWS Cloudwatch. After integrating with watchtower, things are working fine, and all the OCPP logs are logged in a single log stream.
I wanted to understand if there is any way I can create an individual stream for OCPP logs based on the ID of the charger.
Any insights or direction would be of great help.
The text was updated successfully, but these errors were encountered: