Input: internal-messages
Receive internal messages from Hotrod
Field Summary
Field Name | Type | Description | Default |
---|---|---|---|
filter-kind | string | Specifies whether the message originated from the "system" or by the "user" | - |
filter-source | Vec | Specifies what process generated the message. Was it a "server", "agent" or "pipe" | - |
filter-agent | string | Specifies what process generated the message. Was it a "server", "agent" or "pipe" | - |
filter-pipe | string | Specifies the name of the pipe that the message came from. | - |
filter-type | Vec | Specifies that particular types of message ought to match | - |
filter-tag | string | Specifies that messages matched ought to carry a tag with a particular value. This only matches against user-generated messages. | - |
Fields
filter-kind
Type: string
Possible Values: system, user
Specifies whether the message originated from the "system" or by the "user"
Example
Pipe Language Snippet:
filter-kind: system
filter-source
Type: Vec
Specifies what process generated the message. Was it a "server", "agent" or "pipe"
Example
Pipe Language Snippet:
filter-source: agent
filter-agent
Type: string
Specifies what process generated the message. Was it a "server", "agent" or "pipe"
Example
Pipe Language Snippet:
filter-agent: agent-1
filter-pipe
Type: string
Specifies the name of the pipe that the message came from.
Example
Pipe Language Snippet:
filter-pipe: http_poll_pipe
filter-type
Type: Vec
Specifies that particular types of message ought to match
Example
Pipe Language Snippet:
filter-type: [pipe-is-processing]
filter-tag
Type: string
Specifies that messages matched ought to carry a tag with a particular value. This only matches against user-generated messages.
Example
Pipe Language Snippet:
filter-tag: user-defined-tag-string