RE: Obfusticated data?

Hi, thank you, will try peer out.

For scaling, you are absolutely right, we currently do have a script running on each box to do reporting and archiving.

The issue I am trying to solve is that we then have to managing 50 scripts and not 1 - monitoring the scripts to make sure they are running etc is much more intensive than monitoring one point etc.  

Basically, the complexity of the environment scales in a way that requires more effort even with automation. 

Thank you much for the suggestion!!

Mark


-----Original Message-----
From: Miroslav Lichvar <[email protected]> 
Sent: Monday, October 3, 2022 2:07 AM
To: [email protected]
Subject: Re: [chrony-users] Obfusticated data?

[You don't often get email from [email protected] Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

On Fri, Sep 30, 2022 at 08:33:01PM +0000, Mark Notarus wrote:
> We have been doing that by parsing local logs, which works fine but scales terribly.

What is the issue with scaling? You can could be polling the tracking report, or pushing it from the client to a central location.

> Could someone help me understand the goal of this data deletion?

Here is a draft that described this idea:
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization-04

As a workaround, you can use specify the server as "peer" instead of "server", which will disable the data minimization.

--
Miroslav Lichvar


--
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "help" in the subject.
Trouble?  Email [email protected]


-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]