-
Notifications
You must be signed in to change notification settings - Fork 10
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
s390x Compatibility #250
Comments
Hi @xreip ! I asked in the issue to add support for this platform/arc If guys will add the support of the mentioned platform, I will update the SDK version. |
Hi @xreip ! I built the plugin with the patched SDK on my local machine, how to share the archive with you? ![]() You can check to see if would it work on your machine |
Hi @dmitryk-dk ! Thanks that's really nice ! I didn't know you depend on the grafana sdk for that. I ended just compiling the plugin backend from source on the s390x machine. Installed the plugin from release and then :
We've been ingesting millions of logs in VL since yesterday through opentelemetry collector. Really happy with how it goes. Does your build would bring anything more ? I happily take the compilation full command tho 😁 If you could put the s390x binary in futur releases that would be very nice, but i understand it's a bit more complicated than i thought. Thank you ! |
Before we started to sign the plugin, we used our own make files and built for any platform. To make some additional build is not a big problem, but for the sign process, it should be built via the mage |
Hello @dmitryk-dk , Amazing ! Thank you very much |
Hi! I think we can close this issue because the build was enabled in the release |
Hi,
Would you consider adding a linux/s390x build in your CI/CD ?
I'm currently considering using victorialogs and victoriametrics on this plateform (they both compile on that arch). But i can't really exploit them since the Grafana datasources aren't compatible.
I understand this arch is niche but there's also so few tools easily available...
(Should i create an issue for victoriametrics datasource too ? Strangely the vm plugin "works" while vl doesn't, i guess it falls back to prometheus...)
Thanks
The text was updated successfully, but these errors were encountered: