Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.0-rc4, 6.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- neweng
- query-offsite

Backwards Compatibility:
Fully Compatible
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

In ~~SERVER-48742~~ we now log the new profiler settings whenever they are changed. Since "filter" and "level" are database specific, it is necessary to log the database name on the log line as well; otherwise you can't tell where the profile setting was changed.

is caused by

SERVER-48742 Log whenever profiler settings are changed via setProfilingLevel

Closed

Assignee:: Colin Stolley
Reporter:: Eric Milkie
Participants:: Colin Stolley, Eric Milkie, Githook User
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Oct 05 2022 08:08:29 PM UTC
Updated:: Oct 29 2023 09:32:21 PM UTC
Resolved:: Oct 28 2022 08:27:20 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates