![]() ![]() ![]() # If a label name is longer than this number post metric-relabeling, the entire # Per-scrape limit on length of labels name that will be accepted for a sample. # entire scrape will be treated as failed. # more than this number of labels are present post metric-relabeling, the # Per-scrape limit on number of labels that will be accepted for a sample. # the entire scrape will be treated as failed. # If more than this number of samples are present after metric relabeling # Per-scrape limit on number of scraped samples that will be accepted. # This is an experimental feature, this behaviour could # An uncompressed response body larger than this many bytes will cause the # Reloading the configuration will reopen the file. # File to which PromQL queries are logged. # external systems (federation, remote storage, Alertmanager). # The labels to add to any time series or alerts when communicating with # How long until a scrape request times out. # How frequently to scrape targets by default. They also serve as defaults for other configuration sections. The global configuration specifies parameters that are valid in all other configurationĬontexts. ![]() The other placeholders are specified separately. : a string which is template-expanded before usage.Supported units: B, KB, MB, GB, TB, PB, EB. ![]() : a regular string that is a secret, such as a password.: a string that can take the values http or https.: a string matching the regular expression *.: a valid string consisting of a hostname or IP followed by an optional port number.: a valid path in the current working directory.: a boolean that can take the values true or false.Generic placeholders are defined as follows: To specify which configuration file to load, use the -config.file flag.īrackets indicate that a parameter is optional. This will also reload any configured rule files. Sending a HTTP POST request to the /-/reload endpoint (when the -web.enable-lifecycle flag is enabled). Is not well-formed, the changes will not be applied.Ī configuration reload is triggered by sending a SIGHUP to the Prometheus process or Prometheus can reload its configuration at runtime. To view all available command-line flags, run. Locations, amount of data to keep on disk and in memory, etc.), theĬonfiguration file defines everything related to scraping jobs and their The command-line flags configure immutable system parameters (such as storage Kubernetes tags also integrate perfectly with Dynatrace filters.Prometheus is configured via command-line flags and a configuration file. You can also leverage Kubernetes tags to set up fine-grained alerting profiles. This allows you to easily find and inspect the monitoring results of related processes running in your Kubernetes or OpenShift environment. Kubernetes-based tags are searchable via Dynatrace search. Kubernetes pod UID: Unique ID of the related pod.Kubernetes namespace: Namespace to which the containerized process is assigned.Kubernetes full pod name: Full name of the pod the container belongs to.Kubernetes container: Name of the container that runs the process.Kubernetes base pod name: User-provided name of the pod the container belongs to.Such properties and annotations can be used when specifying automated rule-based tags.Īdditionally Dynatrace detects the following properties that can be used for automated rule-based tags and property-based process group detection rules. Automatic detection of Kubernetes properties and annotationsĭynatrace detects Kubernetes properties and annotations. These tags and rules can be changed and adapted any time and will apply almost immediately without any change to the monitored environment or applications. This enables you to use automated tagging rules, based on existing or custom metadata, to define your filter sets for charts, alerting, and more. Dynatrace automatically detects and retrieves all Kubernetes and OpenShift annotations for pods that are monitored with a OneAgent code module. For Kubernetes-based applications, you can simply use Kubernetes annotations. We recommend that you define additional metadata at the deployed system. This enables you to automatically organize and filter all your monitored Kubernetes/OpenShift application components. Dynatrace automatically derives tags from your Kubernetes/OpenShift labels. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |