BerndP

## Thoughts about capabilities and formats ### The local logging must be unified * each log line must have the same structure * each log line must have the same...

Whoever has ideas that need to be considered, please speak up! :) This is an open discussion to take into account as many thoughts as possible from the start. I...

Hmm thinking again about Larry's idea of the hostname parameter, i come to a different conclusion ... 'hostname' => either Cacti or the device I'm open, I believe to match...

Comment on the timestamp: If possible, at least internally we should go for milliseconds, as it is much more precise and therefore easier to reconstruct the sequence, if for example...

Regarding Graphs and Users: I think we can handle those always as an array. Either it contains 1 element or it contains more, and it is easier to have it...

Logging into a DB in principle has the same constraint .. if the target DB is down -> fails. But in case of Cacti, which is heavily relying on the...

@TheWitness: Sounds okay so far, i am just not too comfortable with that part: "cacti_log() will take mixed input either array or string" I would create a new logging function...

Long standing question i stumbled on while checking the issues for anything related to spikekill ... I realized as well, that in certain situations a spike might be still in...