Graylog
App · 11 actions
Search and count your Graylog log messages, pause and resume streams, turn event definitions on and off, search alerts and send log messages. Start a workflow for each new alert or matching message, or when a count of messages crosses a threshold.
Actions
| Action | What it does |
|---|---|
| Count messages | Count the messages that match a search in the last few minutes or hours, such as errors from one server in the last 15 minutes, in all or for each value of a field, to compare with a threshold. |
| Disable event definition | Turn an event definition off, so it stops raising events and alerts, such as while a known problem is being fixed. |
| Enable event definition | Turn an event definition on, so it searches on its schedule and raises events and alerts again. |
| Get system status | Check Graylog's health: whether it is running and processing messages, its search cluster's health (green, yellow or red), its nodes and its system notifications. |
| List event definitions | List the event definitions (Graylog's alert rules) the token can see, with their priority and whether each is enabled. |
| List streams | List the streams the token can see, with whether each is running or paused. |
| Pause stream | Pause a stream, so messages stop being routed into it (and its alerts stop) until it is resumed, such as during planned maintenance. |
| Resume stream | Resume a paused stream, so messages are routed into it again. |
| Search events and alerts | Find the events and alerts Graylog raised in the last few minutes or hours, newest first: all of them, or only alerts, of one event definition, or from a priority up. |
| Search messages | Find the log messages that match a search, in the last few minutes or hours or between two times, newest first. |
| Send log message | Send a message to Graylog through its GELF HTTP input, such as an audit trail of what a workflow did, with fields you choose. |
Count messages
Count the messages that match a search in the last few minutes or hours, such as errors from one server in the last 15 minutes, in all or for each value of a field, to compare with a threshold.
Inputs
- Search query
querytext - What to find, as typed in Graylog's search bar, such as level:3 AND source:web-01 or "payment declined". Leave empty for every message.
- Stream
streamtext - Only messages in this stream. Leave empty for every stream the token can see.
- Time range
sincetext - How far back to look. Defaults to the last hour. A length of time such as 30m or 2d works too, up to 90 days.One of:
5m(Last 5 minutes),15m(Last 15 minutes),1h(Last hour),6h(Last 6 hours),24h(Last 24 hours),7d(Last 7 days),30d(Last 30 days). Default:1h. - From
startdate and time - Instead of the time range: when to start. Leave empty to use the time range.
- To
enddate and time - When to stop. Leave empty for now.
- Count for each
group_bytext - A field to count separately for each of its values, such as source or level. Leave empty for one total.
- Most values
limitnumber - With Count for each: how many of its values to count, most first. Defaults to 10, up to 100.From 1 to 100.
Outputs
countnumber- How many messages matched, in all
endtext- Where it ended, in UTC (ISO 8601)
group_bytext- The field counted by; empty for one total
groupslist- The count for each value of the field counted by, most first
querytext- The Graylog search query that ran; * for every message
starttext- Where the time range began, in UTC (ISO 8601)
streamslist- The streams searched; empty for every stream the token sees
Example output
{
"count": 151,
"end": "2026-11-09T14:30:00.000Z",
"group_by": "source",
"groups": [
{
"count": 97,
"value": "checkout-01"
},
{
"count": 54,
"value": "checkout-02"
}
],
"query": "level:3",
"start": "2026-11-09T14:15:00.000Z",
"streams": []
}Disable event definition
Turn an event definition off, so it stops raising events and alerts, such as while a known problem is being fixed.
Inputs
- Event definition
event_definitiontextRequired - The event definition, by title or id.
Outputs
alerttrue/false- True when it sends notifications, so its events are alerts
descriptiontext- Its description
enabledtrue/false- True when it runs on its schedule
idtext- The event definition's id
last_matchedtext- When it last matched, in UTC (ISO 8601)
prioritynumber- Its priority: 1 Low, 2 Medium, 3 High, 4 Critical
priority_labeltext- Its priority by name, such as High
querytext- The search it runs, if it is a search condition
stream_idslist- The streams it searches
titletext- Its title
typetext- Its kind, such as aggregation-v1 for a search condition
updated_attext- When it was last changed, in UTC (ISO 8601)
Example output
{
"alert": true,
"description": "Error-level payment messages from checkout",
"enabled": false,
"id": "6af392ab573a5d60a357e39b",
"last_matched": "2026-11-09T14:21:10.000Z",
"priority": 3,
"priority_label": "High",
"query": "level:3 AND payment",
"stream_ids": [
"6af39249573a5d60a357e343"
],
"title": "Payment failures",
"type": "aggregation-v1",
"updated_at": "2026-11-02T09:20:01.000Z"
}Enable event definition
Turn an event definition on, so it searches on its schedule and raises events and alerts again.
Inputs
- Event definition
event_definitiontextRequired - The event definition, by title or id.
Outputs
alerttrue/false- True when it sends notifications, so its events are alerts
descriptiontext- Its description
enabledtrue/false- True when it runs on its schedule
idtext- The event definition's id
last_matchedtext- When it last matched, in UTC (ISO 8601)
prioritynumber- Its priority: 1 Low, 2 Medium, 3 High, 4 Critical
priority_labeltext- Its priority by name, such as High
querytext- The search it runs, if it is a search condition
stream_idslist- The streams it searches
titletext- Its title
typetext- Its kind, such as aggregation-v1 for a search condition
updated_attext- When it was last changed, in UTC (ISO 8601)
Example output
{
"alert": true,
"description": "Error-level payment messages from checkout",
"enabled": true,
"id": "6af392ab573a5d60a357e39b",
"last_matched": "2026-11-09T14:21:10.000Z",
"priority": 3,
"priority_label": "High",
"query": "level:3 AND payment",
"stream_ids": [
"6af39249573a5d60a357e343"
],
"title": "Payment failures",
"type": "aggregation-v1",
"updated_at": "2026-11-02T09:20:01.000Z"
}Get system status
Check Graylog's health: whether it is running and processing messages, its search cluster's health (green, yellow or red), its nodes and its system notifications.
Inputs
None.
Outputs
cluster_idtext- The cluster's id
healthytrue/false- True when Graylog is running and processing messages and its search cluster is green
hostnametext- The host name of the node that answered
indexer_statustext- The search cluster's health: green, yellow or red
is_processingtrue/false- True when it is processing messages
lifecycletext- Its state, such as running
node_countnumber- How many nodes there are
nodeslist- The Graylog nodes in the cluster
notificationslist- Graylog's system notifications, which name problems to look at
shardsobject- The search cluster's shards by state
started_attext- When the node started, in UTC (ISO 8601)
timezonetext- Its time zone
versiontext- Graylog's version
Example output
{
"cluster_id": "a01aa45b-13f7-465f-be75-b053605860a0",
"healthy": true,
"hostname": "graylog-01",
"indexer_status": "green",
"is_processing": true,
"lifecycle": "running",
"node_count": 1,
"nodes": [
{
"hostname": "graylog-01",
"is_leader": true,
"last_seen": "2026-11-09T14:29:58.000Z",
"node_id": "9ab13ac4-eb70-421b-bb74-9deaedd6de68"
}
],
"notifications": [],
"shards": {
"active": 6,
"initializing": 0,
"relocating": 0,
"unassigned": 0
},
"started_at": "2026-11-09T08:00:12.994Z",
"timezone": "Etc/UTC",
"version": "6.3.15+3ad654f"
}List event definitions
List the event definitions (Graylog's alert rules) the token can see, with their priority and whether each is enabled.
Inputs
- Title contains
querytext - Only event definitions whose title contains this. Leave empty for all.
- Limit
limitnumber - The most to return. Defaults to 100.From 1 to 1000.
Outputs
countnumber- How many were returned
enabled_countnumber- How many of those returned are enabled
event_definitionslist- The event definitions, by title
totalnumber- How many match in all
Example output
{
"count": 1,
"enabled_count": 1,
"event_definitions": [
{
"alert": true,
"description": "Error-level payment messages from checkout",
"enabled": true,
"id": "6af392ab573a5d60a357e39b",
"last_matched": "2026-11-09T14:21:10.000Z",
"priority": 3,
"priority_label": "High",
"query": "level:3 AND payment",
"stream_ids": [
"6af39249573a5d60a357e343"
],
"title": "Payment failures",
"type": "aggregation-v1",
"updated_at": "2026-11-02T09:20:01.000Z"
}
],
"total": 1
}List streams
List the streams the token can see, with whether each is running or paused.
Inputs
None.
Outputs
countnumber- How many streams there are
paused_countnumber- How many of them are paused
streamslist- The streams, by name
Example output
{
"count": 1,
"paused_count": 0,
"streams": [
{
"created_at": "2026-11-02T09:12:44.000Z",
"description": "Messages from the checkout servers",
"editable": true,
"id": "6af39249573a5d60a357e343",
"index_set_id": "6af39211573a5d60a357e154",
"is_default": false,
"paused": false,
"rule_count": 1,
"title": "Checkout"
}
]
}Pause stream
Pause a stream, so messages stop being routed into it (and its alerts stop) until it is resumed, such as during planned maintenance.
Inputs
- Stream
streamtextRequired - The stream, by name or id. The token's user needs it shared as Manager.
Outputs
created_attext- When it was created, in UTC (ISO 8601)
descriptiontext- What the stream holds
editabletrue/false- False for Graylog's own streams, which can't be paused
idtext- The stream's id
index_set_idtext- The index set it stores messages in
is_defaulttrue/false- True for the Default Stream
pausedtrue/false- True when the stream is paused
rule_countnumber- How many rules route messages into it
stream_idtext- The id of the stream changed
titletext- The stream's name
Example output
{
"created_at": "2026-11-02T09:12:44.000Z",
"description": "Messages from the checkout servers",
"editable": true,
"id": "6af39249573a5d60a357e343",
"index_set_id": "6af39211573a5d60a357e154",
"is_default": false,
"paused": true,
"rule_count": 1,
"stream_id": "6af39249573a5d60a357e343",
"title": "Checkout"
}Resume stream
Resume a paused stream, so messages are routed into it again.
Inputs
- Stream
streamtextRequired - The stream, by name or id. The token's user needs it shared as Manager.
Outputs
created_attext- When it was created, in UTC (ISO 8601)
descriptiontext- What the stream holds
editabletrue/false- False for Graylog's own streams, which can't be paused
idtext- The stream's id
index_set_idtext- The index set it stores messages in
is_defaulttrue/false- True for the Default Stream
pausedtrue/false- True when the stream is paused
rule_countnumber- How many rules route messages into it
stream_idtext- The id of the stream changed
titletext- The stream's name
Example output
{
"created_at": "2026-11-02T09:12:44.000Z",
"description": "Messages from the checkout servers",
"editable": true,
"id": "6af39249573a5d60a357e343",
"index_set_id": "6af39211573a5d60a357e154",
"is_default": false,
"paused": false,
"rule_count": 1,
"stream_id": "6af39249573a5d60a357e343",
"title": "Checkout"
}Search events and alerts
Find the events and alerts Graylog raised in the last few minutes or hours, newest first: all of them, or only alerts, of one event definition, or from a priority up.
Inputs
- Show
includetext - Alerts and events (the default), alerts only, or only events that aren't alerts.One of:
all(Alerts and events),alerts(Alerts only),events(Events that aren't alerts). Default:all. - Event definition
event_definitiontext - Only events of this event definition. Leave empty for all.
- Priority
prioritytext - Only events of this priority or higher.One of:
any(Any priority),2(Medium or higher),3(High or higher),4(Critical only). Default:any. - Search query
querytext - Only events whose message or fields match this, such as payment or fields.order_id:48213. Leave empty for all.
- Time range
sincetext - How far back to look. Defaults to the last hour. A length of time such as 30m or 2d works too, up to 90 days.One of:
5m(Last 5 minutes),15m(Last 15 minutes),1h(Last hour),6h(Last 6 hours),24h(Last 24 hours),7d(Last 7 days),30d(Last 30 days). Default:1h. - From
startdate and time - Instead of the time range: when to start. Leave empty to use the time range.
- To
enddate and time - When to stop. Leave empty for now.
- Limit
limitnumber - The most to return. Defaults to 50.From 1 to 1000.
Outputs
alert_countnumber- How many of those returned are alerts
countnumber- How many were returned
eventslist- The events, newest first
totalnumber- How many match in all
Example output
{
"alert_count": 1,
"count": 1,
"events": [
{
"alert": true,
"event_definition_id": "6af392ab573a5d60a357e39b",
"event_definition_title": "Payment failures",
"fields": {},
"group_by_fields": {},
"id": "01M73Q9W89TWW2JEDCJCKS9TGR",
"key": "",
"message": "Payment failures",
"priority": 3,
"priority_label": "High",
"source": "graylog-01",
"source_streams": [
"6af39249573a5d60a357e343"
],
"timestamp": "2026-11-09T14:21:07.418Z",
"timestamp_processing": "2026-11-09T14:22:00.297Z"
}
],
"total": 1
}Search messages
Find the log messages that match a search, in the last few minutes or hours or between two times, newest first. Get each message with its time, source and the fields you choose, and all of them as text for an AI step or a message.
Inputs
- Search query
querytext - What to find, as typed in Graylog's search bar, such as level:3 AND source:web-01 or "payment declined". Leave empty for every message.
- Stream
streamtext - Only messages in this stream. Leave empty for every stream the token can see.
- Time range
sincetext - How far back to look. Defaults to the last hour. A length of time such as 30m or 2d works too, up to 90 days.One of:
5m(Last 5 minutes),15m(Last 15 minutes),1h(Last hour),6h(Last 6 hours),24h(Last 24 hours),7d(Last 7 days),30d(Last 30 days). Default:1h. - From
startdate and time - Instead of the time range: when to start. Leave empty to use the time range.
- To
enddate and time - When to stop. Leave empty for now.
- Fields
fieldstext - Other fields to get with each message, separated by commas, such as level, http_status. The time, source and message always come back.
- Limit
limitnumber - The most messages to return. Defaults to 50, up to 1000.From 1 to 1000.
- Order
ordertext - Newest messages first (the default), or oldest first.One of:
newest(Newest first),oldest(Oldest first). Default:newest.
Outputs
countnumber- How many messages were returned
endtext- Where it ended, in UTC (ISO 8601)
limit_reachedtrue/false- True when the limit was reached, so there may be more
messageslist- The matching messages, in the order asked for
querytext- The Graylog search query that ran; * for every message
starttext- Where the time range began, in UTC (ISO 8601)
streamslist- The streams searched; empty for every stream the token sees
texttext- Every message as text, one a line with its time and source, ready for an AI step or a message
Example output
{
"count": 1,
"end": "2026-11-09T14:30:00.000Z",
"limit_reached": false,
"messages": [
{
"fields": {
"level": 3,
"order_id": "48213"
},
"id": "3bebbab0-dd51-11f1-b786-e2a8d2599290",
"message": "payment declined for order 48213: card expired",
"source": "checkout-01",
"timestamp": "2026-11-09T14:21:07.418Z"
}
],
"query": "level:3 AND payment",
"start": "2026-11-09T13:30:00.000Z",
"streams": [
"6af39249573a5d60a357e343"
],
"text": "2026-11-09T14:21:07.418Z checkout-01: payment declined for order 48213: card expired (level=3, order_id=48213)"
}Send log message
Send a message to Graylog through its GELF HTTP input, such as an audit trail of what a workflow did, with fields you choose. Needs the input's address on the connection.
Inputs
- Message
messagetextRequired - The text to log, such as Refund 48213 approved.
- Level
leveltext - How serious it is. Defaults to Informational.One of:
0(Emergency),1(Alert),2(Critical),3(Error),4(Warning),5(Notice),6(Informational),7(Debug). Default:6. - Source
sourcetext - The host or app to log it as, such as billing-workflow. Defaults to lodol.
- Fields
fieldsobject - Extra fields to send with it, by name, such as order_id and workflow, which you can search for in Graylog.
- Details
full_messagetext - A longer text kept with the message, such as a stack trace.
- Time
timestampdate and time - When it happened. Leave empty for now.
Outputs
fieldsobject- The extra fields sent with it, by name
levelnumber- Its level, as a syslog severity from 0 (Emergency) to 7 (Debug)
level_labeltext- Its level by name, such as Informational
messagetext- The message sent
senttrue/false- True once the GELF HTTP input took the message
sourcetext- The source it was sent as
timestamptext- The time it carries, in UTC (ISO 8601)
Example output
{
"fields": {
"order_id": "48213",
"workflow": "refunds"
},
"level": 6,
"level_label": "Informational",
"message": "Refund 48213 approved by the finance workflow",
"sent": true,
"source": "lodol",
"timestamp": "2026-11-09T14:30:00.000Z"
}