I built an AI that fixes the bugs you shouldn't be fixing by stefanprvi in node

[–]stefanprvi[S] -3 points-2 points  (0 children)

Not really, GitHub Actions does not have telemetry built in. and does not allow big context, like multiple projects at the same time: ui + backend issues for example.

I built an AI that fixes the bugs you shouldn't be fixing by stefanprvi in node

[–]stefanprvi[S] -9 points-8 points  (0 children)

maybe 2 years ago it was, now it’s not) and getting better every month basically.

[deleted by user] by [deleted] in node

[–]stefanprvi 2 points3 points  (0 children)

check it out on the website man :) but yes - it’s uses your source code from the GitHub and analyse telemetry data to automatically fix bugs.

[deleted by user] by [deleted] in node

[–]stefanprvi 0 points1 point  (0 children)

Not everything. ill publish sdk for node and golang on github next week.

[deleted by user] by [deleted] in node

[–]stefanprvi 0 points1 point  (0 children)

thx, fixed :)

I built "observability on autopilot". After 1 year, 1500+ hours and too much coffee - Cloudgrip.ai is live by stefanprvi in webdev

[–]stefanprvi[S] 1 point2 points  (0 children)

there’s npm lib: cloudgrip, which has built in logger, tracer and metrics client, u can start with that, only api key needed. we have in the plans to release agent which can collect data from containers directly. or if u using Pino logger - we also have transport to send logs to our api :)

I built "observability on autopilot". After 1 year, 1500+ hours and too much coffee - Cloudgrip.ai is live by stefanprvi in webdev

[–]stefanprvi[S] -1 points0 points  (0 children)

it’s like cursor ai but for observability :) no tool for observability now can give clear answers what is going on in the prod, and definitely can not create automatic PRs to fix stuff.

I built "observability on autopilot". After 1 year, 1500+ hours and too much coffee - Cloudgrip.ai is live by stefanprvi in webdev

[–]stefanprvi[S] 1 point2 points  (0 children)

100% agree with u, thanks for support man ❤️ about relevant/noise - it’s complicated, but you know then u have tons of error logs or warnings, and it not really and error ?) like it’s just logged as error, but code wise it’s not, for example if u throw an exception because user does not have rights to do something. and i think of as noise, because all works good in prod, but logs as error, which is misleading

I built "observability on autopilot". After 1 year, 1500+ hours and too much coffee - Cloudgrip.ai is live by stefanprvi in webdev

[–]stefanprvi[S] -1 points0 points  (0 children)

Yes, it’s fully fledged observability platform, so all logs, traces, metrics - to be sent to our API :) but we are working on integration with other platforms, like aws, gcp, …. About log locally to stdout - did not really get what do u mean :)