GitLab Analyze:Product Analytics Team Meetings, 22 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Set up product analytics using GraphQL mutation

Description

Max (BE engineer, Analyze::Product Analytics) demonstrates the capabilities added in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/104559

A

Hey folks, my name is Matt wolf, I'm, a senior back-end engineer on the product, analytics team and I'm, going to show you how to initialize a new project with product analytics using a new graphql API.

A

So this is really an art in question: I'm just going to walk through it, because it's quite a few steps and uh yeah it'd be good to show it rather than type it I think so. You'll need to enable the feature flag, which I've already done on my GDK I set the dev kit lots of instructions in there. How to do it right should just be a Docker compose up uh and then you'll need to visit the admin settings in your GDK and set all that up feel free to ping me.

A

If you need any help with that, um and then we can get on to show mutation working so assuming Jitsu is up and running um should have all that on Port 8000.

A

uh So let's go and create a new project.

A

A

Copy the full path head over to hit us, so we've created this new mutation project initialize product Analytics, which just takes the project full path as the sole input it Returns the project assuming it finds it. So you can put in whatever information you want. There uh just return full path. You can also return any errors.

A

So by running this we will initialize a background job which we'll set up the clickhouse destination and the Jitsu connection to it. So in theory, once it works, we should see a new connection here which would be gitlab project, slash uh whatever the new ideas 28. Okay, so we'll run this micro. uh This mutation, great, you, can see, there's no errors, so we know it's worked.

A

um I'll give it a second in case the job, so I'm quite ready. Yet we know this page. There we go so we now created that I've got to clickhouse destination with the correct name. You can see no errors. If we run this again, it won't run it again because it knows that the initialization is already complete.

A

So you can run this as many times as you want and nothing will happen uh if you run it twice in quick succession, it will fail because the job holds a lock on it, so it can't run twice while one's still in progress. So if we've got Network latency between gitlab and Jitsu or click out or anything else, um then it won't try and run the job multiple times.

A

That's it. Let me know if you've got any questions.