Custom actions

Custom actions turn values from a log into clickable jumps to Coralogix screens, internal tools, dashboards, or third-party services. Define a URL template once with placeholders that pull fields from the selected log, then trigger the action from any matching log to open the destination with the right context already filled in. No more manual copy-paste between tools.

What you need

To create actions, you need permission to manage actions in your Coralogix account and a dataset that contains the fields you plan to inject into URLs. To trigger an action, the destination must accept browser navigation. Most in-product routes and third-party web apps qualify.

Open the Actions panel

Go to Explore, then Logs.
Select Settings in the upper-right corner. In the Actions section of the settings panel, select Manage Actions.

The Actions panel opens on the right with two sections:

Private: actions only you can see and use.
Shared: actions created by you or others that are visible to the team.

Create an action

From the Actions panel, select Add new action.
Fill in the form:
- Name: the label shown in the action menu and catalog.
- URL template: the destination URL with {{...}} placeholders that pull fields from the selected log. URLs must start with http:// or https://.
- Data type: restricts where the action appears (for example, Logs). Leave blank to show on every supported surface.
- Description: a short note explaining when to use the action.
- Filters: narrow when the action appears by application, subsystem, or other attributes. Toggle Exact match to require an exact value match on every filter.
- Access: Private keeps the action to your account, and Shared makes it visible to teammates under the Shared section of the catalog.
Select Save.

The action appears in the catalog and is immediately available wherever its filters and data type apply.

URL template variables

Use double curly braces ({{ }}) anywhere in the URL template. Three variable namespaces are available:
Variable What it resolves to Example
$d Fields from the selected log, including nested paths. {{$d.trace_id}}, {{$d.log_str.span_id}}
$m Coralogix metadata fields attached to the log. {{$m.applicationName}}, {{$m.subsystemName}}, {{$m.severity}}, {{$m.timestamp}}
$p Page and query context. Values from the current Explore session and the value the user clicked. {{$p.start_date}}, {{$p.end_date}}, {{$p.selected_value}}

Use $p.selected_value when the action should pass the specific value the user clicks on. Actions that include $p.selected_value only appear in the value menu, not in the row-level menu.

JavaScript expressions

Anything inside {{ }} is evaluated as a JavaScript expression. You can branch on field values, build composite strings, or call standard JavaScript functions:

https://example.com/?env={{ $m.subsystemName === "frontend" ? "Front" : "Back" }}

Bracket notation for special characters

For field names that contain hyphens, spaces, or that start with a digit, use bracket notation instead of dot notation:

https://example.com/?id={{$d["order-id"]}}&user={{$d["123_user"]}}

Trigger an action

After saving, an action becomes available wherever its Data type and Filters match the current log.

Run a query in Explore so the grid contains the log you want to act on.
Open the action menu in one of two ways:
- From a log row: open the more actions menu next to the row. Only actions that do not use {{$p.selected_value}} appear here.
- From an attribute value: click the value of any field in the log. Every matching action is listed, and {{$p.selected_value}} resolves to the clicked value.
Select the action. The destination URL opens in a new browser tab with all placeholders replaced.

Example URL templates

Authoring an action follows the same shape every time. Take the destination URL, replace each dynamic value with {{$d.field}}, {{$m.field}}, or {{$p.selected_value}}, paste the result into URL template, give the action a name, and save. The same recipe handles a Coralogix screen, a Grafana board, and a Jira ticket. Only the destination URL changes.

The recipes below cover the most common workflows. Replace the angle-bracketed placeholders (<team>, <your-domain>, and so on) with values from your account, and adjust the field names to match your log shape.

Open the related trace. Jump from a log to its trace, with the time window centered on the log's timestamp. Best when the log carries a trace_id.

https://<team>.coralogix.com/#/tracing/{{$d.trace_id}}?start={{$m.timestamp*1000 - 3000000000}}&end={{$m.timestamp*1000 + 3000000000}}

Pivot to a filtered logs query. Open Explore filtered to logs that share a key with the current log, over the same time range.

https://<team>.coralogix.com/#/explore/logs?queryType=lucene&query=<key>:"{{$d.<key>}}"&from={{$p.start_date}}&to={{$p.end_date}}

Pivot from a log to its spans. Open the Spans dataset filtered to the same trace_id as the current log.

https://<team>.coralogix.com/#/explore/spans?queryType=lucene&query=trace_id:"{{$d.trace_id}}"&from={{$p.start_date}}&to={{$p.end_date}}

Open a RUM session. Move from a log carrying session_id to all events in that user's session.

https://<team>.coralogix.com/#/explore/logs?queryType=lucene&query=cx_rum.session_context.session_id:"{{$d.session_id}}"

Open a Grafana dashboard for the service. Land on a Grafana board pre-filtered to the service that emitted the log.

https://grafana.<your-domain>.com/d/<dashboard-id>/<dashboard-name>?var-service={{$m.subsystemName}}

Create a Jira ticket pre-filled from the log. Open the Jira issue-creation form with the summary and description populated from log fields.

https://<your-atlassian-domain>.atlassian.net/secure/CreateIssueDetails!init.jspa?pid=<jira_pid>&issuetype=<jira_issue_type>&summary={{$d.msg}}&description={{$d.logRecord.body}}

Search the web for the clicked value. Look up an error string, identifier, or message from the log. Use $p.selected_value so the action only appears in the value menu and passes the exact clicked value.

https://www.google.com/search?q={{$p.selected_value}}

Branch the destination by environment. Use a JavaScript ternary to send production logs to one URL and others to a different one.

https://<team>.example.com/{{ $m.subsystemName === "prod" ? "prod-tools" : "staging-tools" }}/incident?id={{$d.incident_id}}

Limitations

Area	Limit
URL scheme	Must start with `http://` or `https://`. Other schemes (`mailto:`, `slack:`, custom protocols) are not supported.
Triggering surface	Actions trigger from individual log rows or attribute values. They are not available from chart visualizations, aggregations, or grouped views.
Value-aware actions	Actions that include `{{$p.selected_value}}` appear only in the attribute-value menu, not on the row-level menu.
Variables	Only the `$d`, `$m`, and `$p` namespaces are supported. References to other namespaces are passed through literally and produce broken URLs.
Authentication	The destination opens in a new browser tab. The user must already be signed in to that destination. Actions cannot pass credentials.

Troubleshoot

Problem	Cause	Resolution
The action does not appear on a log	The action's filters or data type exclude the current log.	Open the action and remove or adjust the filters. Confirm the log is from the right data type.
The action only shows in the value menu, not the row menu	The URL template includes `{{$p.selected_value}}`.	Trigger the action by clicking an attribute value, or remove `$p.selected_value` from the template if you want a row-level action.
The opened URL has empty placeholders	The selected log does not contain the referenced field.	Add a filter to the action so it only appears on logs that include the field, or rewrite the template with a fallback expression.
The action will not save	The URL does not start with `http://` or `https://`.	Prefix the URL with the correct scheme.
A field with a hyphen renders as a JavaScript error	Dot notation cannot reference fields with hyphens, spaces, or leading digits.	Use bracket notation: `{{$d["my-field"]}}`.
Teammates cannot see an action	The action's Access is set to Private.	Edit the action and switch Access to Shared.

Support

Reach the Coralogix customer success team 24/7 via in-app chat or by email at support@coralogix.com.

Need help? Contact Support.

What's new? Find out here.

LLM? Read llms.txt.

Previous Explore actions

Next Query with DataPrime

Variable	What it resolves to	Example
`$d`	Fields from the selected log, including nested paths.	`{{$d.trace_id}}`, `{{$d.log_str.span_id}}`
`$m`	Coralogix metadata fields attached to the log.	`{{$m.applicationName}}`, `{{$m.subsystemName}}`, `{{$m.severity}}`, `{{$m.timestamp}}`
`$p`	Page and query context. Values from the current Explore session and the value the user clicked.	`{{$p.start_date}}`, `{{$p.end_date}}`, `{{$p.selected_value}}`