![]() Note: Configuration values are saved in the configuration file. This path may vary depending on your installation. The configuration file is located at %PROGRAMFILES%\Tableau\Tableau Resource Monitoring Tool\master\config\config.json. For more information, see About Tableau Help. So, you may continue to see the terms in CLI commands and options, installation folders, configuration files. Because changing terms in certain places can causing a breaking change, we maintain the existing terminology. In an effort to align with our company values of Equality, we have changed non-inclusive terminology where possible. To do this using the web interface, see Resource Monitoring Tool Server Configuration. Text - Outputs in a format that is plain text.This topic describes the configuration options you can use using the configuration file. ![]() Shell - Outputs in a format usable in Linux shells such as Bash.PowerShell - Outputs in a format usable in PowerShell prompts and scripts.MachineJson - Outputs in a format of a JSON object without comments and explanation.Json - Outputs in a format of a JSON object.Cmd - Outputs in a format usable in Windows Command Prompt or batch files.The output format in which the API key information is written to standard output. Generate an API key and hash for HTTP authentication. Identifies from which configuration source each effective configuration value is provided. Redacted - The full configuration but sensitive information, such as known secrets, is redacted.Full - The full configuration without any redaction of any values.Full configuration can show sensitive information. This value is mapped into configuration as the Authentication:MonitorApiKey key.Ĭonfiguration level. This value is not mapped into configuration. This value is mapped into configuration as the DiagnosticPort:EndpointName key. Default is This value is mapped into configuration as the Metrics:Endpoints key. This value is mapped into configuration as the Metrics:Enabled key.īindings for the metrics HTTP api. Default is This value is mapped into configuration as the urls key.Įnable publishing of metrics to /metrics route. Synopsis dotnet-monitor config show īindings for the HTTP api. Shows configuration, as if dotnet-monitor collect was executed with these parameters. When specified, artifacts must be egressed using an egress provider. Generates a temporary API key for the dotnet-monitor instance.ĭisables egress of diagnostic artifacts via the HTTP response. It is strongly recommended that this option is not used in production environments. On Linux and macOS, this must be a valid Unix Domain Socket path.ĭisables API key authentication. On Windows, this must be a valid named pipe name. When not specified, dotnet-monitor is in 'connect' mode. Specifying this option places dotnet-monitor into The fully qualified path and filename of the diagnostic port to which runtime instances can connect. Default is trueīindings for the metrics HTTP api. Synopsis dotnet-monitor collect Įnable publishing of metrics to /metrics route. NET applications, allow collecting diagnostic artifacts, and send the results to a chosen destination. Optionsĭisplays the version of the dotnet-monitor utility. NET applications in production environments and to collect diagnostic artifacts (for example, dumps, traces, logs, and metrics) on-demand or using automated rules for collecting under specified conditions. The dotnet-monitor global tool is a way to monitor. To install the latest release version of the dotnet-monitor NuGet package, use the dotnet tool install command: dotnet tool install -global dotnet-monitorĭownload a Docker image for use in multi-container environments: docker pull /dotnet/monitor There are two ways to download dotnet-monitor: This article applies to: ✔️ dotnet-monitor version 6.0.0 and later versions Install
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |