Packages > pkg.pkl-lang.org/pkl-pantry/com.influxdata.telegraf

com.influxdata.telegraf.plugins.inputs.DiskioInput1.8.0

Properties
Methods

module com.influxdata.telegraf.plugins.inputs.DiskioInput extends com.influxdata.telegraf.plugins.inputs.Input

The DiskIO input plugin gathers metrics about disk I/O by device.

Module URI:: package://pkg.pkl-lang.org/pkl-pantry/com.influxdata.telegraf@1.8.0#/plugins/inputs/DiskioInput.pkl
Pkl version:: 0.25.0 or higher
Source code:: DiskioInput.pkl
Known subtypes in package:
Known usages in package:
All versions:

Properties(show inherited)

link

hidden

output: ModuleOutput (pkl.base)Source

The output of this module.

Defaults to all module properties rendered as either Pcf or the format specified on the command line.
link

namepass: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

An array of glob pattern strings.

Only metrics whose measurement name matches a pattern in this list are emitted.
link

namedrop: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

The inverse of namepass.

If a match is found the metric is discarded. This is tested on metrics after they have passed the namepass test.
link

tagpass: Mapping<String, Listing<String>>? (com.influxdata.telegraf.plugins.Plugin)

A table mapping tag keys to arrays of glob pattern strings.

Only metrics that contain a tag key in the table and a tag value matching one of its patterns is emitted.
link

tagdrop: Mapping<String, Listing<String>>? (com.influxdata.telegraf.plugins.Plugin)

The inverse of tagpass.

If a match is found the metric is discarded. This is tested on metrics after they have passed the tagpass test.
link

fieldpass: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

An array of glob pattern strings.

Only fields whose field key matches a pattern in this list are emitted.
link

fielddrop: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

The inverse of fieldpass.

Fields with a field key matching one of the patterns will be discarded from the metric. This is tested on metrics after they have passed the fieldpass test.
link

taginclude: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

An array of glob pattern strings.

Only tags with a tag key matching one of the patterns are emitted. In contrast to tagpass, which will pass an entire metric based on its tag, taginclude removes all non matching tags from the metric. Any tag can be filtered including global tags and the agent host tag.
link

tagexclude: Listing<String>? (com.influxdata.telegraf.plugins.Plugin)

The inverse of taginclude.

Tags with a tag key matching one of the patterns will be discarded from the metric. Any tag can be filtered including global tags and the agent host tag
link

interval: Duration? (com.influxdata.telegraf.plugins.inputs.Input)

How often to gather this metric.

Normal plugins use a single global interval, but if one particular input should be run less or more often, you can configure that here.
link

name_override: String? (com.influxdata.telegraf.plugins.inputs.Input)

Override the base name of the measurement.

Default: name of the input
link

name_prefix: String? (com.influxdata.telegraf.plugins.inputs.Input)

Specifies a prefix to attach to the measurement name.
link

name_suffix: String? (com.influxdata.telegraf.plugins.inputs.Input)

Specifies a suffix to attach to the measurement name.
link

tags: Mapping<String, String>? (com.influxdata.telegraf.plugins.inputs.Input)

A map of tags to apply to a specific input’s measurements.
link

devices: Listing<String>?Source

Devices to collect stats for.

Wildcards are supported, except for disk synonyms like /dev/disk/by-id/.

Default: ["*"] (all devices, including partitions)
link

skip_serial_number: Boolean?Source

Skip gathering of the disk's serial numbers.
link

device_tags: Listing<String>?Source

Device metadata to add as tags, on systems that support it (Linux only). Use 'udevadm info -q property -n ' to get a list of properties. Note: Most, but not all, udev properties can be accessed this way. Properties that are currently inaccessible include DEVTYPE, DEVNAME, and DEVPATH.
link

name_templates: Listing<String>?Source

Templates used to customize the device name tag.

Using the same metadata source as device_tags, you can also customize the name of the device via templates. The 'name_templates' parameter is a list of templates to try and apply to the device. The template may contain variables in the form of '$PROPERTY' or '${PROPERTY}'. The first template which does not contain any variables not present for the device is used as the device name tag. The typical use case is for LVM volumes, to get the VG/LV name instead of the near-meaningless DM-0 name.

Methods(show inherited)

link

function

getClass(): Class (pkl.base)Source

Returns the class of this.
link

function

toString(): String (pkl.base)Source

Returns a string representation of this.

This method is used to convert the values of string interpolation expressions to strings.
link

function

ifNonNull<Result>(transform: (NonNull) -> Result): Result? (pkl.base)Source

Returns this |> transform if this is non-null, and null otherwise.

This method is the complement of the ?? operator and the equivalent of an Option type's map and flatMap methods.
link

function

hasProperty(name: String): Boolean (pkl.base)Source

Tells if this object has a property with the given name.
link

function

getProperty(name: String): unknown (pkl.base)Source

Returns the value of the property with the given name.

Throws if a property with this name does not exist.
link

function

getPropertyOrNull(name: String): unknown? (pkl.base)Source

Returns the value of the property with the given name.

Returns null if a property with this name does not exist.
link

function

toDynamic(): Dynamic (pkl.base)Source

Converts this object to a Dynamic object.
link

function

toMap(): Map<String, unknown> (pkl.base)Source

Converts this object to a Map.
link

function
relativePathTo(other: Module): List<String> (pkl.base)Source

Returns the relative, descendent directory path between this module and other.
Throws if no such path exists.

For example, if module mod1 has path /dir1/mod1.pkl, and module mod2 has path /dir1/dir2/dir3/mod2.pkl, then mod1.relativePathTo(mod2) will return List("dir2", "dir3").

A common use case is to compute the directory path between a template located at the root of a hierarchy (say rootModule.pkl) and the currently evaluated module (accessible via the module keyword):
```
import "rootModule.pkl" // self-import
path = rootModule.relativePathTo(module)
```