Does anyone know if the EnabledLog registry key for Windows can be set to just capture queries being run against web reports or do you have to set the key to “all”?
We had a case where reports were delayed by more than 6 to 12 hours. As suggested by the support team, we set the configuration to “ALL”, after which we were able to identify which specific query or report was consuming excessive time.
1 Like
I’m not entirely sure what you’re looking for in the logs, but I used timing instead of all and this is a query that I ran.
The options are listed in the wiki - Welcome to Wikis
Tue, 01 Jul 2025 11:41:57 -0700 -- /webreports (1484) -- Entering WebReportsRelevanceEvaluator::EvaluateHTML( (ids of it, names of it, names of sites of it) of bes fixlets whose (name of issuer of it as lowercase contains "gbl")
)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/unshortentext (20992) -- Exiting ProcessJSONRequest (245 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering WebReportsConfiguration::UpdateAllValues
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting WebReportsConfiguration::UpdateAllValues (1 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ProcessJSONRequest
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering WebReportsDB::DeleteExpiredLoginSession
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering UserSessionQueries::DeleteExpiredSessionTokens
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting UserSessionQueries::DeleteExpiredSessionTokens (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting WebReportsDB::DeleteExpiredLoginSession (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering UserSessionQueries::CheckLoginSession
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting UserSessionQueries::CheckLoginSession (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering SetUserInfo
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( computer )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( computer ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( computer with extensions )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( computer with extensions ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( action result counts )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( action result counts ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( fixlet )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( fixlet ) (202 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( action )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( action ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( all action )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( all action ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering ResetHashes( site )
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ResetHashes( site ) (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering UserQueries::GetUserInfo
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering SetUserInfo
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting SetUserInfo (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering SetUserSettings
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting SetUserSettings (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting UserQueries::GetUserInfo (1 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering WebReportsODBCDatabase::GetCachedRoles
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting WebReportsODBCDatabase::GetCachedRoles (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering WebReportsDB::SetupPrivilegesFilterAndCheckValidity
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting WebReportsDB::SetupPrivilegesFilterAndCheckValidity (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting SetUserInfo (206 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering LoadVisibleFilterAndCheckValidity
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting LoadVisibleFilterAndCheckValidity (0 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Entering JSON Method: generatereporturl
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting JSON Method: generatereporturl (2 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /json/generatereporturl (19560) -- Exiting ProcessJSONRequest (249 ms)
Tue, 01 Jul 2025 11:41:57 -0700 -- /webreports (1484) -- Exiting WebReportsRelevanceEvaluator::EvaluateHTML( (ids of it, names of it, names of sites of it) of bes fixlets whose (name of issuer of it as lowercase contains "gbl")
) (369 ms)
Looking for web reports queries, who ran them and when.
“HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\Enterprise Server\BESReports” /v EnabledLogs
Possible values in that registry key are:
all, databases, debug, critical, performance or memory
I have a feeling “all” is my only choice.
If you all would be so kind, HCL Software - Sign In
What does timing do and where is it explained what each option does other than all?
I don’t have those details, but will ask our Dev team