postgres_exporter | A PostgreSQL metric exporter for Prometheus | Analytics library

 by   prometheus-community Go Version: v0.12.0 License: Apache-2.0

kandi X-RAY | postgres_exporter Summary

kandi X-RAY | postgres_exporter Summary

postgres_exporter is a Go library typically used in Analytics, Prometheus applications. postgres_exporter has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

A PostgreSQL metric exporter for Prometheus
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              postgres_exporter has a medium active ecosystem.
              It has 2140 star(s) with 627 fork(s). There are 45 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 168 open issues and 302 have been closed. On average issues are closed in 185 days. There are 44 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of postgres_exporter is v0.12.0

            kandi-Quality Quality

              postgres_exporter has 0 bugs and 0 code smells.

            kandi-Security Security

              postgres_exporter has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              postgres_exporter code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              postgres_exporter is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              postgres_exporter releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.
              It has 2358 lines of code, 73 functions and 11 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of postgres_exporter
            Get all kandi verified functions for this library.

            postgres_exporter Key Features

            No Key Features are available at this moment for postgres_exporter.

            postgres_exporter Examples and Code Snippets

            No Code Snippets are available at this moment for postgres_exporter.

            Community Discussions

            QUESTION

            Connecting to database from prometheus_exporter
            Asked 2022-Feb-20 at 16:52

            To collect Postgres metrics in prometheus, postgres_exporter is used. Containerization is not used, everything is done natively. Hardware metrics are collected in a prometheus through a job. To collect database metrics, I need to connect the prometheus_exporter to the database. Tell me how to configure the connection to the database. postgres_exporter has no configuration files. Шs it possible to do this via environment variables?

            prometheus.yml:

            ...

            ANSWER

            Answered 2021-Dec-16 at 08:45

            Is it possible to do this via environment variables?

            Yes, it is possible. Here is the list of supported variables: https://github.com/prometheus-community/postgres_exporter#environment-variables

            How to configure the connection to the database

            A simple example to launch from console:

            Source https://stackoverflow.com/questions/70345507

            QUESTION

            pgpool node detached for no reason?
            Asked 2021-Dec-02 at 22:43

            I have a two-node PostgreSQL cluster running on VMs where each VM runs both the pgpool service and a Postgres server.

            due to insufficient memory configuration the Postgres server crashed, so I've bumped the VM memory and the changed Postgres memory config in the postgresql.conf file. since that memory changes the slave pgpool node detaches every night at a specific time, though when looking at node_exporter metrics regarding CPU, load, processes disk usage or memory didn't show any spikes or sudden changes.

            the slave node detaching happened before but not day after day. I've stumbled upon this thread and read this part of the documentation about the failover but Since the Postgres server didn't crash and existing connections to the slave node were working (it kept serving existing connections but didn't take new ones) so network issues seemed irrelevant, especially after consulting with our OPS team on whether they noticed any abnormal network or DNS activity that could explain that. Unfortunately, they didn't notice any interesting findings.

            I have pg_exporter, postgres_exporter and node_exporter on each node to monitor the server and VM behavior, what should I be looking for to debug this? what should I ask of our OPS team to check specifically? our pgpool log file only states the failure to access the other node but no exact reason, as the aforementioned docs say:

            Pgpool-II does not distinguish each case and just decides that the particular PostgreSQL node is not available if health check fails.

            could it still be a network\DNS issue? and if so. how would I confirm this?

            thnx for reading and taking your time to assist me in this conundrum

            ...

            ANSWER

            Answered 2021-Dec-02 at 22:41

            that was interesting

            If summing the gist of it,

            it was part of the OPS team infrastructure backups

            Now the entire process went like that:

            setting the ambiance: we run on-prem on top of VMWare vCenter cluster backing up on the infra side with VMWare VM snapshot and Veeamm VM backup where the vmdk files\ESXi datastores reside on a NetApp storage based on NFS.

            when checking node exporter metrics in Node Exporter Full Dashboard I saw network traffic drop in the order of up to 2 packets per second for about 5 to 15 minutes consistently through the last few months, increasing dramatically in phenomenon length in the last month (around the same time late at night).

            Rough illustration:

            After checking again with our OPS team they indicated it could be the host configurations\Veeam Backups.

            It turns out that because the storage for the VMs (including the one that runs the Veeam backup) is attached via network and not directly on the ESXi hosts, the final snapshot saved\consolidated at that late-night time -

            node detaches every night at a specific time

            With the way NFS works with disk locking (limiting IOPs to existing data) along with the high IOPs requirements from the Veeam backup cause the server to hang\freeze and sometimes on rare occasions even a VM restart. here's the quote from the Veeam issue doc:

            The snapshot removal process significantly lowers the total IOPS that can be delivered by the VM because of additional locks on the VMFS storage due to the increase in metadata updates

            the snapshot removal process will easily push that into the 80%+ mark and likely much higher. Most storage arrays will see a significant latency penalty once IOP's get into the 80%+ mark which will of course be detrimental to application performance.

            This issue occurs when the target virtual machine and the backup appliance [proxy] reside on two different hosts, and the NFSv3 protocol is used to mount NFS datastores. A limitation in the NFSv3 locking method causes a lock timeout, which pauses the virtual machine being backed up [during snapshot removal].

            Obviously, that would interfere at the very least with Postgres functionality especially configured as a cluster with replication that requires a near-constant connection between the Postgres servers. A similar thread on SO using a different DB server

            a solution is suggested including solving the issue presented in the last quote in this link, though for the time being, we removed the usage of Veeam backup for sensitive VMs until the solution can be verified locally (will update in the future if tried and fixed issue)

            additional incidents documentation: similar issue case, suggested solution info from Veeam, third party site solution (around the same problem as a temp fix as I see it), Reddit thread acknowledging the issue and suggesting options

            Source https://stackoverflow.com/questions/70033375

            QUESTION

            How to use same labels in a deployment?
            Asked 2020-Apr-13 at 14:33

            I'm trying to pass same label to a deployment, Both deployments have different image and environment variables. I'm using the same label so i can group the metrics together.

            But the deployment is failing. Can someone please point me a workaround or is it because of the api version i'm using?

            Deployment1:

            ...

            ANSWER

            Answered 2020-Apr-13 at 13:51

            Kubernetes uses the labels and selectors to control the replicas of your Deployments, check the example below available in k8s doc:

            Source https://stackoverflow.com/questions/61188984

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install postgres_exporter

            This package is available for Docker:.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/prometheus-community/postgres_exporter.git

          • CLI

            gh repo clone prometheus-community/postgres_exporter

          • sshUrl

            git@github.com:prometheus-community/postgres_exporter.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Analytics Libraries

            superset

            by apache

            influxdb

            by influxdata

            matomo

            by matomo-org

            statsd

            by statsd

            loki

            by grafana

            Try Top Libraries by prometheus-community

            windows_exporter

            by prometheus-communityGo

            elasticsearch_exporter

            by prometheus-communityGo

            PushProx

            by prometheus-communityGo

            json_exporter

            by prometheus-communityGo

            ipmi_exporter

            by prometheus-communityGo