Project

General

Profile

Actions
Copy link

Refactor #19534

closed

Excessive amount of log messages around db field encryption

Added by Lukas Zapletal almost 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Logging
Target version:
1.15.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/4529, https://github.com/theforeman/foreman/pull/4548
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Foreman logs tremendous amount of messages about db field encryption. Major issues: Every en/decryption is logged at info level:

Successfully decrypted field for XYZ

Every attempt to decrypt unencrypted field is reported via debug (annoying in dev mode):

String does not start with the prefix 'encrypted-' XYZ

We should not log success scenarios at all (maybe into TRACE level if we had one) and we need to decrease amount of logs for the other actions, like the annoying "String does not start" messasges.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Refactor #19558: Improve orchestration queue loggingClosedLukas Zapletal05/16/2017Actions
Actions
Copy link
 #1

Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman/pull/4529 added
Actions
Copy link
 #2

Updated by Lukas Zapletal almost 7 years ago

  • translation missing: en.field_release set to 248

Daniel, I am proposing this for 1.15.1 as this is constantly flooding our logs.

Actions
Copy link
 #3

Updated by The Foreman Bot almost 7 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4533 added
Actions
Copy link
 #4

Updated by Lukas Zapletal almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Dominic Cleal almost 7 years ago

  • Pull request deleted (https://github.com/theforeman/foreman/pull/4533)

04d9f6e has the incorrect ticket number, it should have referred to #19558.

Actions
Copy link
 #6

Updated by The Foreman Bot almost 7 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4548 added
Actions
Copy link
 #7

Updated by The Foreman Bot almost 7 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4533 added
Actions
Copy link
 #8

Updated by Lukas Zapletal almost 7 years ago

  • Pull request deleted (https://github.com/theforeman/foreman/pull/4533)

04d9f6e has the incorrect ticket number, it should have referred to #19558

Actions
Copy link
 #9

Updated by Lukas Zapletal almost 7 years ago

Actions
Copy link

Also available in: Atom PDF