Create Default Log Options for Search
See original GitHub issueAs a convenience for request and response logging we should compile a list of log-safe headers and query parameters. These lists should be used to built a default HttpLogOptions
that could be retrieved through a static getter if the user wants to mutate the default log options.
@tg-msft @bryevdv @xirzec @heaths as this will be applicable to other languages as well.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Default Log File Settings for Web Sites <logFile> - IIS
In the Logging pane, select the log file format in the Format box, and then type the path to the directory where you...
Read more >Configure default resource settings for Logging | Google Cloud
Any default settings that you change apply only to resources that are created after the configuration is complete; the new settings don't apply...
Read more >Configuring Logging | Apache Solr Reference Guide 6.6
Solr logs are a key way to know what's happening in the system. There are several ways to adjust the default logging configuration....
Read more >git-log Documentation - Git
This option also changes default diff format for merge commits to ... This can be used to find the set of changes in...
Read more >Advanced Git Log | Atlassian Git Tutorial
If you don't like the default git log format, you can use git config 's aliasing functionality to create a shortcut for any...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’d also suggest
$select
as an allowed query parameter.We’re having internal discussions around whether field names are considered “sensitive data” that might need to stay in the region of the customer’s search service, so logging
$select
by default might be problematic for the same reason as$filter
would be, at least for the query APIs (its usage for the various List<Resource> APIs is innocuous).