Search Results for "can"

...Also, it can be replaced with special values to insert the tag, ECS metadata, or a random string in the name. It can achieve higher throughput and will consume less CPU and memory.

...Output Plugins write metrics to various destinations. New plugins are designed to be easy to contribute, pull requests are welcomed and we work to incorporate as many pull requests as possible. You can try Telegraf right in your browser in the Telegraf playground. Telegraf shares the same minimum requirements as Go.

...A Kinesis Data Stream uses the partition key that is associated with each data record to determine which shard a given data record belongs to. For example, if your logs come from Docker containers, you can use container_id as the partition key, and the logs will be grouped and stored on different shards depending upon the id of the container they were generated from. As the data within a shard are coarsely ordered, you will get all your logs from one container in one shard roughly in order. Nested partition key is supported and you can use -> to point to your target key which is nested under another key. ...

...However, we are pausing development on it and will focus on the high-performance version instead. If the features of the higher performance plugin are sufficient for your use cases, please use it. It can achieve higher throughput and will consume less CPU and memory. This plugin has been tested with Fluent Bit 1.2.0+. It may not work with older Fluent Bit versions. We recommend using the latest version of Fluent Bit as it will contain the newest features and bug fixes. We distribute a container image with Fluent Bit and these plugins.

...The plugin is written in Go, packaged for easy installation via the krew plugin manager, and exposes flags to control namespace scoping, label selectors, and condition filters so you can narrow what’s shown. It defaults to searching namespaced objects in the same namespace as the root resource, but can also traverse cluster-wide objects when asked.

This is a Helm plugin giving you a preview of what a helm upgrade would change. It basically generates a diff between the latest deployed version of a release and a helm upgrade --debug --dry-run. This can also be used to compare two revisions/versions of your helm release.