You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-explorer/k2bridge.md
+24-28Lines changed: 24 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,47 +6,43 @@ ms.author: orspodek
6
6
ms.reviewer: guregini
7
7
ms.service: data-explorer
8
8
ms.topic: conceptual
9
-
ms.date: 03/11/2020
9
+
ms.date: 03/12/2020
10
10
---
11
11
12
12
# Visualize data from Azure Data Explorer in Kibana with the K2Bridge open-source connector
13
13
14
-
K2Bridge (Kibana-Kusto Bridge) enables you to use Azure Data Explorer as the data source and to visualize that data in Kibana. K2Bridge is an open-source containerized application which acts as a proxy between a Kibana instance and an Azure Data Explorer cluster. This article describes how to use K2Bridge to create that connection.
14
+
K2Bridge (Kibana-Kusto Bridge) enables you to use Azure Data Explorer as the data source and to visualize that data in Kibana. K2Bridge is an [open-source](https://github.com/microsoft/K2Bridge) containerized application which acts as a proxy between a Kibana instance and an Azure Data Explorer cluster. This article describes how to use K2Bridge to create that connection.
15
15
16
16
K2Bridge translates Kibana queries to Kusto Query Language (KQL) and sends the Azure Data Explorer results back to Kibana.
17
17
18
18

19
19
20
-
K2Bridge supports Kibana’s Discover tab, where you can:
20
+
K2Bridge supports Kibana's Discover tab, where you can:
21
21
* Search and explore the data
22
22
* Filter results
23
23
* Add or remove fields in the results grid
24
24
* View record content
25
25
* Save and share searches
26
26
27
-
The image below shows a Kibana instance bound to Azure Data Explorer by K2Bridge. The search experience is in Kibana, and the overall look and feel is as usual.
27
+
The image below shows a Kibana instance bound to Azure Data Explorer by K2Bridge. The user experience in Kibanais unchanged.
The K2Bridge connector source code is on [GitHub](https://github.com/microsoft/K2Bridge).
32
-
33
31
## Prerequisites
34
32
35
33
Before you can visualize data from Azure Data Explorer in Kibana, have the following ready:
36
34
37
35
*[Helm V3](https://github.com/helm/helm#install), the Kubernetes package manager
38
-
* Azure Kubernetes Service (AKS) cluster, or any other Kubernetes cluster (version 1.14 to version 1.16 have been tested and verified). If you need an AKS cluster, see the AKS Quickstart guide[using the Azure CLI](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough) or [using the Azure portal](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)
39
-
* An Azure Data Explorer cluster, including:
36
+
* Azure Kubernetes Service (AKS) cluster, or any other Kubernetes cluster (version 1.14 to version 1.16 have been tested and verified). If you need an AKS cluster, see Deploy an AKS cluster[using the Azure CLI](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough) or [using the Azure portal](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)
37
+
* An [Azure Data Explorer cluster](create-cluster-database-portal.md), including:
40
38
* The Azure Data Explorer cluster's URL
41
39
* The database name
42
40
43
-
For more information, see: [Create an Azure Data Explorer cluster and database](create-cluster-database-portal.md)
44
41
* An Azure AD service principal authorized to view data in Azure Data Explorer, including:
45
42
* The Client ID
46
43
* The Client Secret
47
44
48
-
> [!Note]
49
-
> A service principal with 'Viewer' permission is recommended. It is discouraged to use higher permissions.
45
+
A service principal with 'Viewer' permission is recommended. It is discouraged to use higher permissions.
50
46
51
47
*[Set the cluster's view permissions for the Azure AD service principal](https://docs.microsoft.com/azure/data-explorer/manage-database-permissions#manage-permissions-in-the-azure-portal).
52
48
@@ -103,7 +99,7 @@ By default, K2Bridges's Helm chart references a publicly available image located
The complete set of configuration options is [here](https://github.com/microsoft/K2Bridge/blob/master/docs/configuration.md).
102
+
In [Configuration](https://github.com/microsoft/K2Bridge/blob/master/docs/configuration.md) you can find the complete set of configuration options.
107
103
108
104
1. The command output will suggest the next Helm command to run to deploy Kibana. Optionally, run:
109
105
@@ -119,17 +115,17 @@ By default, K2Bridges's Helm chart references a publicly available image located
119
115
120
116
1. Expose Kibana to the end users. There are multiple methods to do so. The method you use largely depends on your use case.
121
117
122
-
Example:
118
+
For example:
123
119
124
120
Expose the service as a LoadBalancer service. To do so, add the following parameter to the K2Bridge Helm install command ([above](#install-k2bridge-chart)):
125
121
126
-
`--set service.type=LoadBalancer`
127
-
128
-
Then run:
122
+
`--set service.type=LoadBalancer`
123
+
124
+
Then run:
129
125
130
-
```bash
131
-
kubectl get service -w -n k2bridge
132
-
```
126
+
```bash
127
+
kubectl get service -w -n k2bridge
128
+
```
133
129
The output should look like:
134
130
135
131
```bash
@@ -144,7 +140,7 @@ In a new Kibana instance:
144
140
1. Navigate to Management.
145
141
1. Select **Index Patterns**.
146
142
1. Create an index pattern.
147
-
The name of the index must **exactly match** the table name or function name, without an asterisk. You can copy the relevant line from the list.
143
+
The name of the index must exactly match the table name or function name, without an asterisk. You can copy the relevant line from the list.
148
144
149
145
> [!Note]
150
146
> To run on other Kubernetes providers, change the Elasticsearch storageClassName in `values.yaml` to fit the one suggested by the provider.
@@ -159,33 +155,33 @@ When Azure Data Explorer is configured as a data source for Kibana, you can use
159
155
160
156

161
157
162
-
1. If your data has a time-filter field, you can specify the time range. At the upper-right of the page, set a **time filter**. By default, Discover shows data for the last 15 minutes.
158
+
1. If your data has a time-filter field, you can specify the time range. At the upper-right of the page, set a time filter. By default, Discover shows data for the last 15 minutes.
1. The results table shows the first 500 records. You can **expand a document** to examine its field data in either JSON or table formats.
162
+
1. The results table shows the first 500 records. You can expand a document to examine its field data in either JSON or table formats.
167
163
168
164

169
165
170
-
1. By default, the results table includes columns for the document _source and the time field (if it exists). You can **choose specific columns** to be added to the results table by selecting **add** next to the field name in the left sidebar.
166
+
1. By default, the results table includes columns for the document _source and the time field (if it exists). You can choose specific columns to be added to the results table by selecting **add** next to the field name in the left sidebar.
0 commit comments