Komodor External Links ⛓

Custom links allow you to connect your systems and create easy navigation from Komodor to your external logging, metrics, ticketing & documentation systems, which helps to ensure that troubleshooting is performed with as much relevant context as possible.

How Does It Work?

Komodor generates the link based on a link template. After adding the template, Komodor generates the links in each one of the screens.

Use Komodor Smart Links to connect Komodor to any system that you have:

Common Use-Cases

Here are a few examples of common use cases:

Add a link on Komodor's availability issues to the logging system dashboard (like Kibana, which is pre-filtered with values like the relevant cluster name, namespace, Pod name, and the relevant timeframe.
Add a link on Komodor's availability issues to relevant metrics dashboards (Grafana / DataDog / NewRelic) with pre-filtered values like cluster name, namespace, Pod name, and the relevant timeframe.
Add a link from Komodor to a relevant internal documentation page.
Add a link from Komodor to a relevant support ticketing system.

How To Add?

Go into one of the services, click on one of the events, go to the links section (in availability issues, it will be in the deploy section), and click on "add external link".
Fill the information where prompted:

The link can be defined to be on a cluster-wide scope.

How To Template Your Links?

Go to the relevant system to which you want to add a link in Komodor.
Filter the dashboard with the values that you want to create a deep link that can be templated.
Template the link using this documentation.

Common Examples

DataDog Service Logs

https://app.datadoghq.com/logs?query=service%3Ae${service}&cols=host%2Cservice&index=%2A&messageDisplay=inline&stream_sort=desc&viz=timeseries&from_ts=${epochStart}&to_ts=${epochEnd}&live=true

DataDog Failed Pod's Logs

https://app.datadoghq.com/logs?query=service%3A${service}%20pod_name%3A${failedPod}&cols=service&index=%2A&messageDisplay=inline&stream_sort=time%2Cdesc&viz=stream&from_ts=${epochStart}&to_ts=${epochEnd}&live=false

DataDog Pods Dashboard

https://app.datadoghq.com/dash/integration/30322/kubernetes-pods-overview?tpl_var_cluster=${cluster}&tpl_var_deployment=${service}&tpl_var_namespace=${namespace}&from_ts=${epochStart}&to_ts=${epochEnd}&live=true

Logz.io / Kibana Failed Pods's Logs

https://app.logz.io/#/dashboard/kibana/discover?_a=(columns:!(message),filters:!(),index:'logzioCustomerIndex*',interval:auto,query:(language:lucene,query:'params.kubernetes.pod_name%20%3D%20${failedPod}'),sort:!(!('@timestamp',desc)))&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:'${timestempStart=yyyy-MM-dd'T'HH:mm:ss.SSS}Z',to:'${timestempEnd=yyyy-MM-dd'T'HH:mm:ss.SSS}Z'))&accountIds=138818&switchToAccountId=138818

Grafana Pod Metrics

http://local.grafana.com/d/6581e46e4e5c7ba40a07646395ef7b23/kubernetes-compute-resources-pod?orgId=1&var-datasource=default&var-cluster=&var-namespace=$(namespace}&var-pod=${failedPod}&from={epochStart}&to=${epochEnd}

Grafana Service Metrics

http://104.154.113.136:60001/d/a164a7f0339f99e89cea5cb47e9be617/kubernetes-compute-resources-workload?orgId=1&var-datasource=default&var-cluster=&var-namespace=${namespace}&var-type=deployment&var-workload=${service}&from=${epochStart}&to=${epochEnd}

Loki Failed Pod's Logs

http://local.grafana.com/d/fRIvzUZMz111/logging-dashboard-via-loki?orgId=1&var-container=${yaml[spec.template.spec.containers[0].name]}&var-pod=${failedPod}&var-stream=All&var-searchable_pattern=&from=${epochStart}&to=${epochEnd}

Loki Deployment Logs

http://104.154.113.136:60001/d/fRIvzUZMz111/logging-dashboard-via-loki?orgId=1&refresh=5s&var-container=${yaml[spec.template.spec.containers[0].name]}&var-pod=All&var-stream=All&var-searchable_pattern=&from=${epochStart}&to=${epochEnd}

ArgoCD Application

https://local.argocd.app/applications/argocd/${yaml[metadata.labels['argocd.argoproj.io/instance']]}?view=tree