👋 Hey author here sorry about that. It
# 💻creators-and-apify
a
👋 Hey author here sorry about that. It was for a feature I am testing on my own account to have a tool that could calculate actor margins including third party external costs. It dosen't send any data unless the user had an apifyhub api key setup in the extension (Which can only be done in local dev mode for my own account atm) I am have pushed update to remove this now and will seperate it out into it's own seperate extension, sorry about this miss on my part and no data was shared apart from my own. And yes feel free to use @igolaizola or create your own.
(For context the API endpoints don't have a nice way to get cost's, only about ~40% my own runs return it. So I requested the feature here, in meantime i was looking at other ways on how I could do this. Didn't realised it pushed out of dev again, my bad) https://discord.com/channels/801163717915574323/1075487274424352888/1547565403503591454
Repo here if you wish to clone / checkout / clone. Along with it's git history if you wish to check out what it done before. https://github.com/awseeley/apify-analytics-plus Relevant line from last version it would not attempt to sync, unless an Apifyhub api key as added. https://github.com/awseeley/apify-analytics-plus/blob/96ef7756f52debac734cda5292d5945723b1b9df/src/lib/hub.js#L152-L153
p
@Andrew - there is no easy way to measure run costs. You basically have to measure your own network bytes, runtime, memory, etc. in the code at runtime. then save it someplace external. then augment with any other external services you might be using. This approach gets you close to 100% accuracy - but its a big pain to setup.
a
Yeah I tried to do that, but it still ended somewhat off. As I couldn't see any way that the CU rate was exposed for a given account. Even assuming they were all default 0.20 it was a bit off. Which lead me down this path of testing locally via extension 🫠 . Sliver lining is I do have is pretty much matched now with also tracking third party costs.
i
@Andrew thanks for explaining it!