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

1.0 fixes, adds ability to monitor multiple servers, and future save file #22

Merged
merged 55 commits into from
Nov 7, 2024

Conversation

featheredtoast
Copy link
Collaborator

@featheredtoast featheredtoast commented Oct 19, 2024

Allow for collections to parameterize server name and save file.

Add new -hostnames arg that is a comma separated value list of servers to watch and update, EG -hostnames server1:8080,server2:9090,server3:8080 - this is exposed as a url label to metrics so interested parties can watch multiple servers at once.

save_name label is "default" for now until FRM can provide a save name.

Also fix up some discrepancies with ficsit remote monitoring's values. We still do not have power values back yet but they're coming

@AP-Hunt
Copy link
Owner

AP-Hunt commented Oct 20, 2024

Thanks for this @featheredtoast. I'm overall happy with the proposed changes and the rational, there's just one doc block to add.

@featheredtoast
Copy link
Collaborator Author

Just pushed a few fixes, wanted more stuff configurable via env vars. gonna test a little more but it's looking good now. will update docs.

@featheredtoast
Copy link
Collaborator Author

just updating, FRM has a few more updates to make it more 1.0 compatible, so I'll update this PR with those.

Meanwhile, would you mind terribly much if we updated how readme generation is done? From what I understand, we're using a golang template to generate the table, and then a batch script to search+replace the readme template... Can we update this to just use golang templates through-and-through?

That way I'd be able to generate new readme tables on non-windows, which is my primary daily driver

@AP-Hunt
Copy link
Owner

AP-Hunt commented Nov 4, 2024

Yeah I'm completely fine with that. I don't use Windows for anything anymore, so I really should update the tooling full stop.

(Apols for the very slow reply. I wanted to wait until you'd finished making the changes you were making ... then I forgot I was waiting)

@featheredtoast
Copy link
Collaborator Author

All good, I think I'm almost done here, FRM 1.2(?) has become much more stable and I don't anticipate this mod needing too many more changes on this.

I'll ping you once I update the tooling steps and then this should be good to merge in

@featheredtoast
Copy link
Collaborator Author

@AP-Hunt I believe this is in a good state now

@AP-Hunt
Copy link
Owner

AP-Hunt commented Nov 7, 2024

Thanks for all your work on this @featheredtoast. I don't have the capacity to test these changes, so I'm going to have to trust that they work.

I've reviewed the non-FRM specific bits though, and I'm happy with them.

I'll merge this and cut a release.

@AP-Hunt AP-Hunt merged commit b186216 into AP-Hunt:main Nov 7, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants