Comments (6)
Besides that, I guess it's a good idea. I'd then go and disable vertica driver from the basic installation, and instead point at your vendor-maintained exporter.
Hi @burningalchemist , sorry to comment on a closed issue.
Our team works with Vertica since a long time and we decided to give the "official" Vertica exporter a try. Unfortunately, it is not very well implemented, doesn't seem very well maintained and has some important issues currently. Later we realised that it is actually a fork of your SQL exporter, which I just tried and everything is working really well and as expected.
For this reason, please reconsider on removing the Vertica driver from your exporter and instead on keeping it 🙏.
Kudos and thanks for your excellent SQL exporter!
EDIT: I'm considering fixing a particular issue we just found (a panic) but I would rather contribute fixes back to this fork than the Vertica one. I will open an issue first and then a PR.
from sql_exporter.
Hi @hhromic, gotcha! Thanks a lot for your feedback! We keep it in-tree then. 🙂👍
from sql_exporter.
No worries. With the details you supplied we consider it constructive criticism. Will follow up with you on the issues you logged. We apprecaite you taking the time to provide feedback. Regards,
from sql_exporter.
Hey Stephen, thanks for letting me now. 👍
It'd be great to know about the breaking changes you identified.
Besides that, I guess it's a good idea. I'd then go and disable vertica driver from the basic installation, and instead point at your vendor-maintained exporter.
My email for the contacts (just in case): oss[at]szyubin[dot]me
Kind regards,
Sergei
from sql_exporter.
Hi @hhromic,
I was a bit surprised at your comments regarding our Vertica Prometheus Exporter. We took the basic burningalchemist exporter, made it Vertica only, and added a lot of enhancements and documentaiton. We've done 3 releases since October's release. We've only had one issue reported that ended up being a missing Vertica role on the customer's end. Please provide details on our Exporter's Github page (https://github.com/vertica/Vertica-Prometheus-Exporter) and let us know what issues you faced and why you feel it's not well implemented or maintained. We'd appreciate some feedback so we can either correct or clarify your various issues and concerns. Regards,
from sql_exporter.
Hi @verticacrossman,
First of all, apologogies for the rather harsh comment I made regarding the Vertica fork. It was a bit late yesterday and was quite frustrated by that fork not working as needed. On the other hand, the fork here worked exactly like we need and thus I mostly wanted the devleoper to not drop Vertica support in the official binaries.
The extra documentation in the Vertica fork seems good and is appreciated but is not clear what are the enhancements you mention in comparison to the original fork here. Perhaps it would be a good idea to clarify that in your repository as we didn't find a reason to prefer the Vertica fork over the SQL exporter version.
We will continue using the SQL exporter at the time being, but when we have a chance we will give the Vertica fork another try so we can report our feedback to your repository as well. 👍
from sql_exporter.
Related Issues (20)
- 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
- [helm] Support getting data-source-name from an existing secret HOT 12
- Ignore no rows returned HOT 6
- Better handling of NULL return values in certain cases HOT 6
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.