This endpoint acts as a proxy to forward HTTP POST request from tracers to the serverless_flare endpoint, allowing tracer flares to be triggered via remote config, improving the support experience by automating the collection of logs.ĬWS: Ability to send a signal to a process when a rule was triggered. The Kubernetes State Metrics Core check now collects kubernetes_.ĪPM: Added a new endpoint tracer_flare/v1/. This is accessible through the agent diagnose command.Īdd FIPS mode support for Network Device Monitoring productsĪdded support for collecting Cloud Foundry container names without the Cluster Agent. You can start using this new check now by manually setting the environment variable DD_ORCHESTRATOR_EXPLORER_RUN_ON_NODE_AGENT to true.Īdds the following CPU manager metrics to the kubelet core check: kubernetes_manager.pinning_errors_total, kubernetes_manager.pinning_requests_total.Īdd a diagnosis for connecting to the agent logs endpoints. In the next release, this new check will replace the current pod check in the Process Agent. The orchestrator check is moving from the Process Agent to the Node Agent. The Python implementation may be removed in a future version of the Agent. Set legacy_mode_v2: true to revert to the Python implementation of the check. See the Python regular expression docs and the Go regular expression docs for more information on the supported regular expression syntax. If you do not use these options, then no configuration changes are necessary. For example, Go regular expressions do not support lookahead or lookbehind assertions. All legacy_mode: false configuration options are backwards compatible except for some regular expressions used in the included_messages and excluded_messages options.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |