This guide will help you use our Rules CRUD-API to create, read, update or delete rules and rule groups using an API.
In order to send an external request, the request headers should contain the following:
Content-Type: application/JSON
Authorization: Bearer {{Alerts, Rules and Tags API key}}. This API key can be found under Data Flow –> API Keys.
** Note that only admin users have access to the Rules API, So the Alerts, Rules and Tags API key will be visible only for admin users.
First, make sure to select the correct API endpoint for your Account region
Cluster Region
Base API Endpoint
Europe (.com)
https://api.coralogix.com/api/v1/external/
US (.us)
https://api.coralogix.us/api/v1/external/
India (.in)
https://api.app.coralogix.in/api/v1/external/
Sweden (.eu2.)
https://api.eu2.coralogix.com/api/v1/external/
Singapore (sg.com)
https://api.coralogixsg.com/api/v1/external/
Groups API
Request type
URL
Body
Create
POST
https://api.coralogix.com/api/v1/external/group
"name" (string) - the name for the rules group (Mandatory)
"description" (string) - the description for the rules group (an empty string is set on default)
"enabled" (boolean) - indicates rather the group will be enabled or not when created (set to true on default)
"creator" (string) - the name of the group creator (set to "Coralogix external API" on default)
"ruleMatchers" (array of objects) - the group filters for passing through the group rules only a subset of logs. Each object in the array should contain the field for the matcher and the constraint. The field must be one of applicationName, subsystemName, or severity, and the constraint (string) that will be the value for the chosen field (if the field is severity, the value should be one: debug, verbose, info, warning, error, critical)
E.g
[
{
"field":"applicationName",
"constraint":"prod"
},
{
"field":"severity",
"constraint":"info"
}
]
"name" (string) - the updated name for the rules group
"description" (string) - the updated description for the rules group
"enabled" (boolean) - indicates rather the group will be enabled or not after the update
"ruleMatchers" (array of objects) - the group filters for passing through the group rules only a subset of logs. Each object in the array should contain the field for the matcher and the constraint. The field must be one of applicationName, subsystemName, or severity, and the constraint (string) that will be the value for the chosen field (if the field is severity, the value should be one: debug, verbose, info, warning, error, critical)
E.g
[
{
"field":"applicationName",
"constraint":"prod"
},
{
"field":"severity",
"constraint":"info"
}
]
"Rule" [string] - The regex of the rule [must be a regex that can be compiled except for "removefields" in which it must be a comma-separated list of fields to be removed]
timestampextract rule's body must not contain the "rule" field
(Optional) The body is allowed to contain: "SourceField" [string] - If not stated in the body then the default source field will be the log text. If you want to run the rule against any internal log JSON field use text.field_name.field_name2...
(Optional) The body is allowed to contain: "DestinationField" [string] - If not stated in the body then the default destination field will be the log text. If you want to run the rule against any internal log JSON field use text.field_name.field_name2...
In case the rule type is 'extract' or 'block' :
The body is not allowed to contain: "ReplaceNewVal" and "DestinationField"
In case the rule type is 'parse' :
The body is not allowed to contain: "ReplaceNewVal"
In case the rule type is 'jsonextract' :
The body is not allowed to contain: "ReplaceNewVal"
The body must contain "DestinationField" [string] (one of those strings "category", "className", "methodName", "severity", "threadId")
In case the rule type is 'replace' :
The body must contain: "ReplaceNewVal"
In case the rule type is 'timestampextract' :
The body is not allowed to contain: "rule"
The body is not allowed to contain: "DestinationField"
The body should contain meaningful "SourceField" [string] (if not specified by default text field will be set as the source field and the rule will not work. You should set the value as text.Your_Time_Field_Name)
The body must contain "formatStandard" [string] (javasdf, golang, strftime, secondsts, millits, microts, nanots)
The body must contain "timeFormat" [string] (you can see our suggestion for each type of standard, normally you will need to change the format to match your time field string pattern with the while comply to the standard)
In case the rule type is 'removefields' :
The body must contain: "rule" [string] (comma-separated list of fields)
The body may always contain (regardless of type) :
"Description" [string] - a description for the rule
"Enabled" [boolean] - a boolean indicator for rather the rule is activated or not
"Rule" [string] - The regex of the rule [must be a regex that can be compiled except for "removefields" in which it must be a comma-separated list of fields to be removed]
timestampextract rule's body must not contain the "rule" field
(Optional) The body is allowed to contain: "SourceField" [string] - If not stated in the body then the default source field will be the log text. If you want to run the rule against any internal log JSON field use text.field_name.field_name2...
(Optional) The body is allowed to contain: "DestinationField" [string] - If not stated in the body then the default destination field will be the log text. If you want to run the rule against any internal log JSON field use text.field_name.field_name2...
In case the rule type is 'extract' or 'block' :
The body is not allowed to contain: "ReplaceNewVal" and "DestinationField"
In case the rule type is 'parse' :
The body is not allowed to contain: "ReplaceNewVal"
In case the rule type is 'jsonextract' :
The body is not allowed to contain: "ReplaceNewVal"
The body may contain "DestinationField" [string] ( one of those strings "category", "className", "methodName", "severity", "threadId")
In case the rule type is 'replace' :
The body may contain: "ReplaceNewVal"
In case the rule type is 'timestampextract' :
The body is not allowed to contain: "rule"
The body is not allowed to contain: "DestinationField"
The body should contain meaningful "SourceField" [string] (if not specified by default text field will be set as the source field and the rule will not work. You should set the value as text.Your_Time_Field_Name)
The body must contain "formatStandard" [string] (javasdf, golang, strftime, secondsts, millits, microts, nanots)
The body must contain "timeFormat" [string] (you can see our suggestion for each type of standard, normally you will need to change the format to match your time field string pattern with the while comply to the standard)
In case the rule type is 'removefields' :
The body must contain: "rule" [string] (comma-separated list of fields)
The body may always contain (regardless of type) :
"Description" [string] - a description for the rule
"Enabled" [boolean] - a boolean indicator for rather the rule is activated or not
The body should contain the JSON object you got from executing the GET request (copy and paste the output of the GET request to the body of the POST request *without changing anything*)
A message stating "Group and Rules transformed successfully" will be prompt once the transfer completed.
NOTE
When moving rules from one account to another keep in mind that the rules groups you imported are concatenated after the existing rules groups, we do not override existing groups by default. If you want to override the existing groups you should first remove them entirely and then import
In order to get the groupId so you could use it with the different requests’ URLs, in your account Data Flow –> Parsing Rules. Click on any group and the browser URL will show the groupId. The ruleId on the other hand can only be retrieved when executing a GET request to get a certain rule/group or when getting all the rules of the account.
Oh no!We didn’t find anything for “”,
