Worked, thanks.
Regards,
Nagarjuna
On Wed, Dec 16, 2020 at 5:31 PM L.walid (PowerM) wrote:
> Great, so your replica is synced, can you replace this on your queries.yml
> and test.
>
> Best regards,
> --
> Walid Largou
> Solution Archi
log_delay
---
0
(1 row)
Regards,
Nagarjuna
On Wed, Dec 16, 2020 at 5:27 PM L.walid (PowerM) wrote:
> Can you try this one :
>
> SELECT CASE WHEN pg_last_wal_receive_lsn() = pg_last_wal_replay_lsn()
>
> THEN 0
>
> ELSE EXTRACT (EPOCH FROM now() - pg_last_xact_replay_timestamp(
pid | usesysid | usename | application_name | client_addr |
client_hostname | client_port | backend_start |
backend_xmin | state | sent_lsn | write_lsn | flush_lsn |
replay_lsn | write_lag | flush_lag | replay_lag | sync_priority |
sync_state |rep
*metric* ?*
>>>>
>>>> Best regards,
>>>> --
>>>> Walid Largou
>>>> Solution Architect / Service Delivery Manager
>>>> Mobile : +212 621 31 98 71
>>>> Email :
m.ma
>>> 320 Bd Zertouni 6th Floor, Casablanca, Morocco
>>> --
>>> https://www.powerm.ma
>>> Power Maroc #1 IBM Business Partner – Power Maroc
>>> This message is confidential .Its contents do not cons
his message is confidential .Its contents do not constitute a commitment
>> by Power Maroc S.A.R.L except where provided for in a written agreement
>> between you and Power Maroc S.A.R.L. Any authorized disclosure, use or
>> dissemination, either whole or partial, is prohibited. If yo
. Any authorized disclosure, use or
> dissemination, either whole or partial, is prohibited. If you are not the
> intended recipient of the message, please notify the sender immediately.
>
> On 16 Dec 2020, at 06:43, 'NAGARJUNA D.N' via Prometheus Users <
> prometheus-users@
Would you please someone help?
Trying this also didn't help
- https://github.com/wrouesnel/postgres_exporter/blob/master/queries.yaml
startup script:
ExecStart=/usr/local/bin/postgres_exporter --extend.query-path
/opt/postgres_exporter/queries.yaml
On Monday, December 14, 2020 at 4:52:14 PM UTC+
Hi,
We are running postgres 12.x on 2 VMs (1 master and 1 replica).
We had configured postgres_exporter to ship metrics but we don't see any
metrics exporter for *pg_replication_lag*. Kindly help.
exporter version:
postgres_exporter v0.5.1 (built with go1.11)
Startup file:
/etc/systemd/system/p
r. The ownership of the
> executable itself is not so important.
>
> That /pg-data is okay is what I would expect, since the permission problem
> is further down.
>
> /MR
>
>
> On Wed, Nov 18, 2020, 11:45 'NAGARJUNA D.N' via Prometheus Users <
> promethe
er either as
>>> root or as the postgres user :/
>>>
>>> The other metrics are collected in different ways (from /proc mostly) so
>>> they are not subject to this permission check.
>>>
>>> /MR
>>>
>>> On
e exporter either as
>> root or as the postgres user :/
>>
>> The other metrics are collected in different ways (from /proc mostly) so
>> they are not subject to this permission check.
>>
>> /MR
>>
>> On Tue, Nov 17, 2020 at 6:37 AM 'NAGARJUNA D.N' v
;> happen if it is lacking "search" permission (the execute bit) on any of the
>>>> enclosing directories.
>>>>
>>>> I would recommend giving +rx on all directories in that path (/pg-data,
>>>> /pg-data/postgresql, /pg-data/postgresql
-data/postgresql, /pg-data/postgresql/12 and so on) – either to all
>> (a+rx) or the group that owns them and add the node exporter to that group.
>> I think this is not a security issue because it allows anyone / that group
>> to `ls -l` the directories but not to ac
ause it allows anyone / that group
> to `ls -l` the directories but not to access the files within, unless those
> files' permissions are way too wide.
>
> /MR
>
> On Mon, Nov 16, 2020 at 1:54 PM 'NAGARJUNA D.N' via Prometheus Users <
> promethe...@googleg
Hi,
I have an FS mounted for PostgreSQL WAL logs which have limited permissions.
Where the disk usage not reported to Prometheus and am getting the
following error.
*Nov 14 18:22:30 timescale-masterdb node_exporter[7368]: level=debug
ts=2020-11-14T12:52:30.707Z caller=filesystem_linux.go:94
co
16 matches
Mail list logo
