Comments (10)
Hi Kevin,
Yeah, I'd say if there is demand, why not. I'm happy to add deb packages as well. Feel free to share if you already have something. I'll take a look. 👍
I can create a deb package as another artifact that can be downloaded from the Github release page. Would this work for you? I don't think I have the resources to maintain a separate deb repository for one application.
I think it's also possible to submit it to some of the Debian repositories. I might need time to investigate it and would appreciate some help here.
Let me know what you think.
Kind regards,
Sergei
from sql_exporter.
Artifact in the same repository seems just fine to me.
Currently there is a "prometheus-sql-exporter" in the debian repository - I am assuming there are functional differences there; do you have any pointers on the what the differences may be? It seems to have a dependency on postgres:
Reading state information... Done
The following additional packages will be installed:
postgresql-client-common postgresql-common ssl-cert
The following NEW packages will be installed:
postgresql-client-common postgresql-common prometheus-sql-exporter ssl-cert
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 3088 kB of archives.
After this operation, 10.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://cdn-aws.deb.debian.org/debian bullseye/main amd64 postgresql-client-common all 225 [89.3 kB]
Get:2 http://cdn-aws.deb.debian.org/debian bullseye/main amd64 ssl-cert all 1.1.0+nmu1 [21.0 kB]
Get:3 http://cdn-aws.deb.debian.org/debian bullseye/main amd64 postgresql-common all 225 [237 kB]
Get:4 http://cdn-aws.deb.debian.org/debian bullseye/main amd64 prometheus-sql-exporter amd64 0.2.0.ds-6+b17 [2741 kB]
Fetched 3088 kB in 0s (46.7 MB/s)
Preconfiguring packages ...
The answers might play a part in the "naming" of the deb package.
from sql_exporter.
I am attaching a tar.gz of what I've done so far
prometheus-mssql-exporter-0.8.6.tar.gz
Salient points:
- I named the package "prometheus-mssql-exporter" - but of course that's just me; the package file contents and/or names would have to be adjusted for whatever name you use
- ./debian/changelog would need to be built from your pipeline, I suppose
- ./debian/compat set to debhelper version 10 - it worked for me, I don't know really what this implies
- ./debian/control would need to be built from your pipeline, and the Maintainer replaced with your details
- ./debian/prometheus-mssql-exporter.install lists the files that the DEB would need to deploy and their locations; I have opted to have the collector files to reside in /etc/prometheus/prometheus-mssql-exporter.conf.d, and to have the main config file to reside in /etc/prometheus
- ./debian/prometheus-mssql-exporter.postinst creates a user "prometheus-mssql-exporter" user for the service to run as, with home folder /var/lib/prometheus-mssql-exporter (I used other exporters such as node and blackbox to borrow this idea)
- ./debian/prometheus-mssql-exporter.service is the sevice unit file for systemd
- ./debian/rules is the minimum implementation
- ./debian/source/format is the minimum requirement
- ./etc contents is self-explanatory
- ./usr contents is self-explanatory (obviously I renamed the binary)
After I unpack the tar, I cd into the new "prometheus-mssql-exporter-0.8.6" folder and run "dh binary-arch"
When installing, I get a warning "repository is broken has no size information" - I have not figured out how to get rid of this warning, but it works anyhow
Anything else you need from me about this?
Regards, Kevin
from sql_exporter.
...and even though I don't have much free time, yes I would assist with the task of submitting to debian repositories. But I suppose one would need to iron out some things first.
Regards, Kevin
from sql_exporter.
@kampagnol Thanks! I have also limited availability at the moment but I'll try to take a look soon and keep you posted. 👍
from sql_exporter.
Hi @kampagnol! Just a quick update. I've taken a look at packaging sql_exporter
as a package for linux distributions. It looks trivial, so I'll schedule some time and try to integrate it with the current release flow. The package should be available in the list of artifacts for future releases. Stay tuned. :)
As for adding it to the linux repositories, it might be a bit tricky. Some of the embedded drivers (e.g. mssql or snowflake) do not represent FLOSS in terms of licensing, and might be ignored by the community. I'm not familiar with the process, though.
Kind regards,
Sergei
from sql_exporter.
Great news, I'll wait for more feedback!
Regards, Kevin.
from sql_exporter.
Hi @kampagnol, I'm sorry for the silence, there is a lot of stuff going on.
I didn't forget about this issue, though. I've prepared the deb/rpm package provisioning process. I still need to test some OS-specific configuration parameters (e.g. systemd parameters, defaults, etc). But it should be available with the next release.
Cheers,
Sergei
from sql_exporter.
Deb/rpm packages should be available with the next release as downloadable artifacts.
from sql_exporter.
That's great to hear, and many thanks. Looking forward to testing it as soon as it becomes available.
from sql_exporter.
Related Issues (20)
- Possibility to add optional labels HOT 2
- pgBouncer support HOT 9
- Improve constant label naming for target and jobs
- Missing job target labels HOT 8
- Return results even if some query fails HOT 2
- Releases built with incorrect Go toolchain HOT 2
- Add support for ASE database (sybase) HOT 1
- Context deadline exceeded error handling HOT 4
- The problem of specifying a schema when capturing PostgreSQL metrics HOT 6
- Different collector file for each differrent job HOT 1
- Allow to set metric timestamp from query results
- Caching context deadline exceeded result HOT 6
- Context Deadline Exceeded HOT 9
- Support for MSSQL named pipe (np:) and shared memory (lpc:) DSNs HOT 16
- `up` metric to show that database connection was successful HOT 5
- parameter to set log file location HOT 8
- Add custom metrics to expose MSSQL server hostname HOT 1
- can we have the Postgres collector yml file example
- Is it possible to distinguish between the sql exporter process status and the target database? HOT 3
- Scrape each job separately HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sql_exporter.