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: connectors/dashboard/lightdash/yaml.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,33 +59,33 @@ Configure the source type and service name for your Lightdash connector.
59
59
60
60
</ContentSection>
61
61
62
-
<ContentSectionid={2}title="Host and Port"lines="6">
62
+
<ContentSectionid={2}title="Host and Port"lines="3">
63
63
64
64
**Host and Port**: Specify the network location where your Lightdash instance is accessible, combining both hostname and port in a URI format: either `http://hostname:port` or `https://hostname:port`, based on your security needs.
65
65
**Example**: For a local setup, use `http://localhost:8080`; for a server deployment, it might be `https://lightdash.example.com:3000`.
66
66
Ensure the specified port is open and accessible through network firewall settings.
67
67
68
68
</ContentSection>
69
69
70
-
<ContentSectionid={3}title="API Key"lines="7">
70
+
<ContentSectionid={3}title="API Key"lines="8">
71
71
72
72
**API Key**: This key authenticates requests to your Lightdash instance. Keep the API Key secure, sharing it only with authorized applications or users.
**Proxy Authentication**: If your Lightdash instance requires authentication through a proxy server, provide proxy credentials. Proxy authentication controls access to external resources and Lightdash.
Copy file name to clipboardExpand all lines: connectors/dashboard/metabase/yaml.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,19 +59,19 @@ Configure the source type and service name for your Metabase connector.
59
59
60
60
</ContentSection>
61
61
62
-
<ContentSectionid={2}title="Username"lines="6">
62
+
<ContentSectionid={2}title="Username"lines="7">
63
63
64
64
**username**: Username to connect to Metabase, for ex. `user@organization.com`. This user should have access to relevant dashboards and charts in Metabase to fetch the metadata.
65
65
66
66
</ContentSection>
67
67
68
-
<ContentSectionid={3}title="Password"lines="7">
68
+
<ContentSectionid={3}title="Password"lines="8">
69
69
70
70
**password**: Password of the user account to connect with Metabase.
71
71
72
72
</ContentSection>
73
73
74
-
<ContentSectionid={4}title="Host Port"lines="8">
74
+
<ContentSectionid={4}title="Host Port"lines="9">
75
75
76
76
**hostPort**: The hostPort parameter specifies the host and port of the Metabase instance. This should be specified as a string in the format `http://hostname:port` or `https://hostname:port`. For example, you might set the hostPort parameter to `https://org.metabase.com:3000`.
-**Username**: Username to connect to MicroStrategy, e.g., user@organization.com. This user should have access to relevant dashboards and charts in MicroStrategy to fetch the metadata.
57
57
</ContentSection>
58
-
<ContentSectionid={3}title="Password"lines="7">
58
+
<ContentSectionid={3}title="Password"lines="8">
59
59
-**Password**: Password of the user account to connect with MicroStrategy.
60
60
</ContentSection>
61
-
<ContentSectionid={4}title="Host Port"lines="8">
61
+
<ContentSectionid={4}title="Host Port"lines="9">
62
62
-**Host Port**: This parameter specifies the host of the MicroStrategy instance. This should be specified as a URI string in the format http://hostname or https://hostname.
63
63
For example, you might set it to https://demo.microstrategy.com.
-**Project Name**: The name of the project within MicroStrategy that OpenMetadata will connect to, linking to the relevant dashboards and reports for metadata retrieval.
-**Login Mode**: Login Mode for Microstrategy's REST API connection. You can authenticate with one of the following authentication modes: `Standard (1)`, `Anonymous (8)`. Default will be `Standard (1)`.
70
70
If you're using demo account for Microstrategy, it will be needed to authenticate through loginMode `8`.
This parameter specifies the host and port of the Metabase instance. This should be specified as a URI string in the format `http://hostname:port` or `https://hostname:port`.
58
-
For example, you might set it to `http://192.168.1.1:80`.
58
+
For example, you might set it to `http://192.178.1.1:80`.
- Log into [Microsoft Azure](https://ms.portal.azure.com/#allservices).
@@ -120,43 +120,43 @@ To get the client secret, follow these steps:
120
120
- In the Add a client secret pop-up window, provide a description for your application secret, select when the application secret expires, and select Add.
121
121
- From the Client secrets section, copy the string in the Value column of the newly created application secret.
122
122
</ContentSection>
123
-
<ContentSectionid={4}title="tenantId"lines="8">
123
+
<ContentSectionid={4}title="tenantId"lines="9">
124
124
**tenantId**: PowerBI Tenant ID.
125
125
To get the tenant ID, follow these steps:
126
126
- Log into [Microsoft Azure](https://ms.portal.azure.com/#allservices).
127
127
- Search for App registrations and select the App registrations link.
128
128
- Select the Azure AD app you're using for Power BI.
129
129
- From the Overview section, copy the Directory (tenant) ID.
130
130
</ContentSection>
131
-
<ContentSectionid={5}title="scope"lines="9-10">
131
+
<ContentSectionid={5}title="scope"lines="10">
132
132
**scope**: Service scope.
133
133
To let OM use the Power BI APIs using your Azure AD app, you'll need to add the following scopes:
To identify a token authority, you can provide a URL that points to the authority in question.
140
140
If you don't specify a URL for the token authority, we'll use the default value of https://login.microsoftonline.com/.
141
141
</ContentSection>
142
-
<ContentSectionid={7}title="hostPort"lines="12">
142
+
<ContentSectionid={7}title="hostPort"lines="13">
143
143
**hostPort**: URL to the PowerBI instance.
144
144
To connect with your Power BI instance, you'll need to provide the host URL. If you're using an on-premise installation of Power BI, this will be the domain name associated with your instance.
145
145
If you don't specify a host URL, we'll use the default value of https://app.powerbi.com to connect with your Power BI instance.
146
146
</ContentSection>
147
-
<ContentSectionid={8}title="Pagination Entity Per Page"lines="13">
147
+
<ContentSectionid={8}title="Pagination Entity Per Page"lines="14">
148
148
**Pagination Entity Per Page**:
149
149
The pagination limit for Power BI APIs can be set using this parameter. The limit determines the number of records to be displayed per page.
150
150
By default, the pagination limit is set to 100 records, which is also the maximum value allowed.
0 commit comments