Skip to content

Create and Manage Custom Actions

Overview

Custom actions are user-defined, interactive links that can be triggered from any widget within Custom Dashboards. They provide direct interaction with individual data points—allowing you to pivot into deeper investigation paths or launch follow-up workflows. For instance, you can drill down into a specific value, such as a trace ID or region, to view it in another dashboard, or open a external tool, such as a search engine or third-party application, with the data pre-loaded from your dashboard visualization.

Define structured workflows and specify how they're triggered using custom URLs tailored to your data. You have full control over the URL structure, including support for dynamic, data-driven variables—such as response statuses, host names, or container names—so that relevant widget-specific data is automatically passed when the action is executed.

Use custom actions to:

Creating a custom action

At the core of each action is a custom link, which you manually define. You have full flexibility over the link’s structure, including:

  • Destination URL.
  • Variables to pass based on the selected widget data.

These variables allow the link to dynamically adapt depending on what data point is clicked. To get started, see the list of supported variables you can include in your custom links.

Base URL structure

You can use custom links to navigate to different areas of the Coralogix platform.

To construct custom links that navigate between different features—such as various Custom Dashboards views, Infrastructure Resource Catalog, or Real User Monitoring —use the following base URL format

https://<team>.<coralogix_domain>/#/<feature_path>?<optional_query_parameters> 
  • Replace <team> with your team name.
  • Replace <coralogix_domain> with your Coralogix domain, which varies by region.
  • Replace <dashboard_id> with the ID of your custom dashboard. You can find this ID by opening your custom dashboard in the browser and copy it from the URL.
  • Replace <feature_path> with the target Coralogix screen. Each feature has a unique path structure. To find valid examples, see the custom link use cases.

Supported variables

Variables allow you to pass dynamic context into your custom actions—such as a selected label, time range, series name, or value.

For example, to include specific log data, time range, and metadata in your link, you could use a URL like this:

https://<team_name>.coralogix.com/#/dashboards/<target_dashboard>?from={{$p.timeRange.startTime}}&to={{$p.timeRange.endTime}}&var-application={{$l.applicationname}}
VariableVariable typeDescription
$lLabelsUser-managed labels or tags applied to logs or events. These are defined by the user and can be used to classify or group data, such as application or subsystem .
$mMetadataCoralogix metadata fields like timestamp, severity, and others.
$pQuery parametersDashboard level query parameters, including fields such as dashboard variables and time range values such as timeRange.startTime and timeRange.endTime.
$dLog dataThe selected log object, used to extract specific fields directly from a log entry.

Learn more about supported variables and their attributes.

User-managed labels - $l

FieldDescriptionPossible ValuesType
applicationnameThe name of the application generating the eventstring
categoryThe event’s category, such as type or functionstring
classnameThe name of the class where the event occurredstring
computernameThe name of the machine or hoststring
subsystemnameThe specific subsystem of the applicationstring

System metadata - $m

FieldDescriptionPossible ValuesType
timestampTime the event was recorded.-timestamp
severityEvent’s severity level.DebugVerboseInfoWarningErrorCriticalstring
priorityclassIndicates the event's importance.highmediumlowstring
logidUnique identifier for the log.-string

Query parameters - $p

FieldDescriptionPossible ValuesType
timeRange.startTimeStart of the time range.-timestamp
timeRange.endTimeEnd of the time range.-timestamp

Note: The available variables depend on the specific widget and the data displayed in the visualization.

If you modify a widget’s query after creating a custom action—such as changing the Group By field—and the updated data no longer includes a variable used in the action’s URL, a validation warning will appear in the Settings panel next to the affected action. This helps you identify when an action is referencing data that is no longer available. When creating or editing an action, you can also use autocomplete to view the list of valid variables for the current widget configuration.

alt text

The following examples demonstrate how you can use custom links to pass your data context to other dashboards, widgets, and external systems.

A common use case for a custom link is to capture a data point—such as a host, trace ID, status— in a custom dashboard visualization, and view it across multiple dashboards.

For example, your source dashboard has a dashboard variable named hostname, mapped to the log field kubernetes.node.hostname. When selected, this filters all widgets across the dashboard by host. Learn more about dashboard variables.

You can create a custom link that passes the host information to a second custom dashboard, with the following URL:

https://<team_name>.coralogix.com/#/dashboards/<target_dashboard_ID>?var-hostname=<hostname>

Explanation:

  • <team> and <coralogix_domain> should be replaced with your team’s actual values and Coralogix domain (e.g., companyabc-dev.coralogix.com).
  • <target_dashboard_ID> is the ID of the dashboard you want to open.
  • var-hostname is the hostname dashboard variable in the target dashboard that typically represents the fully qualified domain name of the machine or node.
  • {{$d.kubernetes.node.hostname}} dynamically passes the selected host value from the widget into the link.

This custom action ensures that the host variable selected in one dashboard is automatically transferred to the next.

You can use a custom link to pivot from a dashboard directly into Infra Explorer, transferring a specific data attribute to filter or focus your view. For example, one of your widgets tracks logs across different AWS regions, filtering them by severity. You might want to investigate the infrastructure associated with a particular region in greater detail, allowing you to explore the relevant resources directly.

https://<team_name>.coralogix.com/#/infrastructure/monitoring/catalog?menu=All&menuItem=All&search=Region%253A%2520%2522{{$d.awsRegion}}%2522

Explanation:

  • <team> and <coralogix_domain> are replaced with your team's values.
  • {{$d.resource.region}} dynamically inserts the selected region value from the widget into the Resource Catalog query.

This custom action streamlines context-aware navigation from visual data to infrastructure insights—without requiring manual re-entry of search filters.

Troubleshoot error messages

Troubleshooting is a common use case for triggering a custom link to an external search engine. For example, if a an unfamiliar or critical error message appears from one of your dashboard visualizations, you might want to search for more context of its meaning or possible resolutions.

https://www.google.com/search?q=troubleshoot%20{{$d.errorMessage}}

This allows you to navigate directly from visualization to actionable research in a third-party search engine, without manually copying log messages or error codes.

Investigate IP address details

Another practical use case for custom links is to extract an IP address from your logs and pass it to a third-party IP lookup service. This is helpful when you want to understand more about the source of traffic, identify suspicious access patterns, or enrich your alert investigations.

https://whatismyipaddress.com/ip/{{$d.sourceIPAddress}}

This custom link opens a new browser tab that automatically retrieves IP details from the third-party lookup service, using the selected IP address from your dashboard.

Create custom actions

Follow these steps to create custom actions in Custom Dashboards.

  1. In the widget's Settings panel, scroll to the CUSTOM ACTIONS section and click Add action. alt text

  2. In the New custom action modal, name your action and define its destination URL. Click Create to add the action to the dashboard.

    alt text

  3. To save the action in your dashboard, hover over Save in the top right corner of the screen and choose Save or Save As.

    Note: Custom actions are only retained once the dashboard is saved. Leaving the page without saving will discard any new custom actions you’ve created.

    alt text

Access custom actions

How users access data links depends on the type of visualization:

  • In time series widget, the link appears when clicking directly on a point or line.
  • Clicking anywhere in the panel in visualizations such as polystat, gauge, or bar chart brings up the context menu with available links.

Manage custom actions

Edit custom actions

To edit a link: in the Settings panel, hover over the action and click edit-icon Edit action. The edit action modal opens with existing pre-filled for editing.

Delete custom actions

To delete a link, click edit-icon Delete action. The delete action modal opens. Select Delete.

Permissions

Depending on which custom actions you want to manage or trigger, the following permissions are required.
ResourceActionDescription
team-actionsReadConfigView shared custom actions
team-actionsUpdateConfigCreate, update, or delete shared actions
team-actionsExecuteExecute shared actions
team-dashboardsReadAccess Custom Dashboards
team-dashboardsUpdateRequired to save actions