-
Notifications
You must be signed in to change notification settings - Fork 6
TraceHubConfigExplained
TraceHub MVC and Slim use appSettings for configuration. Some of the settings are already explained in other wiki pages, while this page include all settings.
This is to determine if some advanced functions like the Clients button will be shown in the nav bar of the Web page.
Example:
<add key="loggingHub_AdvancedMode" value="true"/>Remarks
Even in the Advanced Mode, the Clients button may not be available if the IP address of the Web browser is not within what defined in loggingHub_AllowedIPAddresses.
This is the maximum number of traces to be displayed in the Web page in queue. The max value allowed is 10000, and values larger than this will become 10000. The min value is 200, and values smaller than this will become 200. If the buffer size is fulfilled, the older traces on the top will be removed from the page while the incoming traces are added at the bottom.
Example:
<add key="loggingHub_ClientBufferSize" value="2000"/>Hints:
To contain large volume of traces or persist, you may add TraceHub Console along with respective trace listeners to your ecosystem.
This is to allow anonymous access to SignalR functionalities of TraceHub. TraceHub Slim is using this setting.
Example:
<add key="loggingHub_Anonymous" value="true" />This is to define IP addresses and ranges and allow clients from these IP addresses to upload traces. This setting is generally used by TraceHub Slim.
Example:
<add key="loggingHub_AllowedIpAddresses" value="12.123.223.123, 192.168.0.1-192.168.0.255, 192.168.1.0/24, 191.168.0.0/255.255.255.0"/>To restrict client accesses to TraceHub, you may refer to IP Security of IIS. Obviously the IP addresses defined by IP Security of IIS should cover what defined in loggingHub_AllowedIpAddresses, otherwise, no transportation of SignalR could be established in the first place.
This is to define IP addresses and ranges and allow clients from these IP addresses to read traces pushed by the server. This setting is generally used by TraceHub Slim.
Example:
<add key="loggingHub_AllowedIpAddressesForView" value="12.123.223.123, 192.168.0.1-192.168.0.255, 192.168.1.0/24, 191.168.0.0/255.255.255.0"/>This setting is handy if you have many sources uploading traces, but just want very few locations being able to read traces, and you want to use TraceHub Slim rather than TraceHub MVC that requires authentication.
By default, TraceHub will buffer trace messages from multiple origins (servers) for 200 milliseconds in a Priority Queue, presuming that all server nodes have the clocks synchronized and the latency is no more than 200 milliseconds. This will ensure trace messages arrive at the client side in time stamp order. The value range is 100 - 2000.