blog: telemetry v2 blogpost #1031
Draft
+745
−596
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There are a lot of unrelated changes in this PR |
commit: |
sam-goodwin
reviewed
Sep 30, 2025
|
|
||
| ## Why we left posthog | ||
|
|
||
| Alchemy used to use posthog for our platform analytics. While posthot was really easy to set up (see our example here) it simply didn't meet our needs. One of our most important metrics is the number of projects that use alchemy. In order to get quality analytics from posthog we would need to give each alchemy project a dedicated project id and maintain that id as a project grows; this proves to be quite a challenging issue. We can't just use a UUID and store it somewhere as alchemy doesn't have a config file, and we don't expect the `.alchemy` directory to be committed. We explored using various other solutions such as the root commit hash (unavailable for partial clone) or the git upstream url (breaks if origin changes) but none of these solutions were reliably enough. Ultimately we decided to identify projects based on multiple factors instead of having a single id. |
There was a problem hiding this comment.
Perhaps a new line break at "this proves to be quite a challenging issue."?
alchemy-web/src/content/docs/blog/2025-09-30-reworking-alchemys-telemetry.md
Show resolved
Hide resolved
|
|
||
| Between not having a consistent project id, and multiple of our team members having experience with datalakes and large scale analytics solutions, we decided to switch to a more developer-oriented solutions. Just having all of our own data in-house so we can do whatever we want with it as we please. | ||
|
|
||
| That being said posthog is great at what it does, and we will continue to use posthog for our web analytics where its still a great fit! |
There was a problem hiding this comment.
Jacob pointed out we should do the whole "compliment sandwhich thing" since we want to make it clear posthog isn't bad
Comment on lines
+13
to
+22
| We started with a few criteria | ||
| - we wanted an OLAP database since they are great for analytics | ||
| - we wanted something SQL based so we didn't have to learn a new query language | ||
| - we wanted something to avoid the big cloud providers as we don't support GCP or Azure yet, and we are in the middle of revamping our AWS resources as part of our [effect](https://effect.website/) based rewrite. | ||
| - we wanted something quick as the team was getting frustrated with our current analytics solution. | ||
| - preferrably a nice controlplane api | ||
|
|
||
| After looking at the options we decided to go with Clickhouse Cloud. It had a great controlplane api so making a resource was easy. First we generate a typescript api from Clickhouse's OpenAPI spec, then we write our alchemy resource. | ||
|
|
||
| This is a simplified example, but we're omitting clickhouse's plethora of customization options for brevity, but the full resource is available [here](https://github.com/alchemy-framework/alchemy/blob/main/alchemy/src/clickhouse/service.ts). |
There was a problem hiding this comment.
Try and avoid bullet point lists. Tell the story. I don't think we've told the story of needing a compound key.
Comment on lines
+24
to
+32
| ```ts | ||
| export const Service = Resource( | ||
| "clickhouse::Service", | ||
| async function ( | ||
| this: Context<Service>, | ||
| id: string, | ||
| props: ServiceProps, | ||
| ): Promise<Service> { | ||
| const api = createClickhouseApi(); |
There was a problem hiding this comment.
Way too much code. Why is this useful for the blog?
|
Blog started off great but then lost its narrative form. Let's try and convert it into narrative structure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.