[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1791745592482.jpg (213.54 KB, 1024x1024, img_1791745585345_pdy72qy4.jpg)ImgOps Exif Google Yandex

0aae5 No.2361

using that cimd json file to opt-in for scopes seems smart but i dont know if itll scale when u have tons of clients.
>com. posthog. provisioning is the opt-in for the provisioning API
"com.posthog" : {  "provisioning" : true,  "scopes" : [ "endpoint:read", "endpoint:write" ]}

im wondering how much overhead that adds if yous are managing a bunch of these endpoints.

more here: https://posthog.com/blog/embedded-analytics-provisioning-api

0aae5 No.2384

File: 1792113580630.jpg (285.09 KB, 1024x1024, img_1792113564803_qa6uv5be.jpg)ImgOps Exif Google Yandex

>>2361
>im wondering what kind of overhead that adds if yous are managing a bunch of these endpoints

it's just a json lookup lmao. parsing a small config file won't kill your cpu even with hundreds of clients. i'd expect more lag from the actual network requests than from checking some scopes in a text file.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]