Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add faq for sl error #4532

Merged
merged 9 commits into from
Nov 30, 2023
2 changes: 2 additions & 0 deletions website/docs/docs/dbt-cloud-apis/sl-jdbc.md
Original file line number Diff line number Diff line change
Expand Up @@ -352,6 +352,8 @@ semantic_layer.query(metrics=['food_order_amount', 'order_gross_profit'],

## FAQs

<FAQ path="Troubleshooting/sl-alpn-error" />

- **Why do some dimensions use different syntax, like `metric_time` versus `[Dimension('metric_time')`?**<br />
When you select a dimension on its own, such as `metric_time` you can use the shorthand method which doesn't need the “Dimension” syntax. However, when you perform operations on the dimension, such as adding granularity, the object syntax `[Dimension('metric_time')` is required.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ import AvailIntegrations from '/snippets/_sl-partner-links.md';
- <span><a href="https://docs.getdbt.com/docs/dbt-cloud-apis/sl-api-overview" target="_self">{frontMatter.meta.api_name}</a></span> to learn how to integrate and query your metrics in downstream tools.
- [dbt Semantic Layer API query syntax](/docs/dbt-cloud-apis/sl-jdbc#querying-the-api-for-metric-metadata)
- [Hex dbt Semantic Layer cells](https://learn.hex.tech/docs/logic-cell-types/transform-cells/dbt-metrics-cells) to set up SQL cells in Hex.
- [Resolve 'Failed APN'](/faqs/Troubleshooting/sl-alpn-error) error when connecting to the dbt Semantic Layer.

</VersionBlock>

Expand Down
3 changes: 0 additions & 3 deletions website/docs/docs/use-dbt-semantic-layer/gsheets.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,7 @@ To use the filter functionality, choose the [dimension](docs/build/dimensions) y
- For categorical dimensiosn, type in the dimension value you want to filter by (no quotes needed) and press enter.
- Continue adding additional filters as needed with AND and OR. If it's a time dimension, choose the operator and select from the calendar.



**Limited Use Policy Disclosure**

The dbt Semantic Layer for Sheet's use and transfer to any other app of information received from Google APIs will adhere to [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.


2 changes: 2 additions & 0 deletions website/docs/docs/use-dbt-semantic-layer/tableau.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,3 +80,5 @@ The following Tableau features aren't supported at this time, however, the dbt S
- Filtering on a Date Part time dimension for a Cumulative metric type
- Changing your date dimension to use "Week Number"

## FAQs
<FAQ path="Troubleshooting/sl-alpn-error" />
11 changes: 11 additions & 0 deletions website/docs/faqs/Troubleshooting/sl-alpn-error.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
title: I'm receiving an `Failed ALPN` error when trying to connect to the dbt Semantic Layer.
description: "To resolve the 'Failed ALPN' error in the dbt Semantic Layer, create a SSL interception exception for the dbt Cloud domain."
sidebar_label: 'Use SSL exception to resolve `Failed ALPN` error'
---

If you're receiving a `Failed ALPN` error when trying to connect the dbt Semantic Layer with the available [data integration tool](/docs/use-dbt-semantic-layer/avail-sl-integrations), it typically happens when connecting from a computer behind a corporate VPN or Proxy, such as Zscaler.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved

To fix this, add an SSL interception exception for the dbt Cloud domain in your settings.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding a bit of context on why the error occurs might help users work with their IT department to figure out. Maybe something like:

The problem is due to the proxy interfering with the TLS handshake. The Semantic Layer uses gRPC/HTTP2 to connect, so if your proxy does not support this you'll need to add an exception for the dbt Cloud domain. If your proxy does support this, you'll need to make sure it's configured correctly to allow ALPN, or create an exception for the dbt Cloud domain.


This issue is common with integrations like Tableau, DBeaver, Datagrip, ADBC, or JDBC.
Loading