Openldap Master/Slave replication removing cn & gidNumber from group (on slvae) instead of just a member

I have configured a second Openldap server to be a slave of the first: (Overlay was already enabled) dn: olcDatabase={2}bdb,cn=config changetype: modify add:olcSyncrepl olcSyncrepl: {0}rid=001 provider=ldap://******* binddn=”cn=*****,dc=*****,dc=*****,dc=*,dc=” bindmethod=simple credentials=***** searchbase=”dc=*,dc=****,dc=,dc=**” type=refreshAndPersist retry=”5 5 300 +” timeout=1 When I test by deleting a memberUid from a group on the first server, the second server sees this…

Prometheus: scrape interval is 1m, but resolution is still 15s

tl;dr: My scrape interval is 1m, yet I have a 15s resolution. Why? My prometheus configuration includes a job to scrape kong metrics: – job_name: kong_blue honor_timestamps: true scrape_interval: 1m scrape_timeout: 10s metrics_path: /metrics scheme: https dns_sd_configs: – names: – … Consequently, when on the targets tab in the HTML interface, we can see that…