4 ms·

Currently working as part of https://treblle.com https://treblle.com, a tool that makes it super easy to understand what’s going on with your APIs and the apps

Currently working as part of https://treblle.com https://treblle.com, a tool that makes it super easy to understand what’s going on with your APIs and the apps that use them. It has features like real time monitoring, error tracking, auto generated documentation and more. Would love your feedback!

alek_m 5y ago
Looks good, congrats on the funding. I would love to see being implemented in more languages.
- cindreta 5y ago
  thank you very much! hope we get to help a lot of developers
throwaway123xxx 5y ago
I really like your website, qn: how did you make it? I can see how this would be useful as I'm building an API. The free tier is almost too generous and I think I'd be more inclined to pay for this if the free tier had about 1K free API calls and the smallest package was < $30 a month. May differ for others though. In terms of log retention, does anything prevent me from just replicating and storing the logs myself? If so log retention as feature differentiation is a bit superfluous imo. I think some of the features you offer could potentially be behind a paywall. Either way, looks really nice and I am considering being a customer when my team grows a bit more. Good luck!
- cindreta 5y ago
  Hi there i’m the founder of Treblle and also the guy who developed it all;) So the website itself is built using HTML/CSS/JS on the front-end and PHP/MYSQL/LARAVEL on the back-end. We didn’t use any fancy frameworks for the front-end because we managed to do what we want just with CSS. Plus it really helps with performance and loading times if you cut down on JS frameworks. To make sure it scales we use a lot of AWS services on top of Laravel Vapor. If you have any in depth questions about the tech stack let me know. Thank you for your comments! I am glad you would consider it. We originally had a 30 dollar package but thought that it might be to many options. We will adjust that based on your feedback :) When you say "replicating and storing the logs myself". It's not just about the RAW logs - it about who gets to see them and how. Because Treblle allows you to search those logs and say something like "Give me all requests for endpoint X withing a Y time frame that were made from New York, US". So yeah you could be logging thing to CloudWatch but it will just be logs who are not readable to the average person in my opinion. When you share a request from Treblle anybody can understand it, it's full of information that the original log doesn't have like the API version, device information, server information, location data and much more. Personally as a developer i also hate when you have to buy the biggest package just so you can get the feature you want. I find it sleazy. This way you literary pay for the requests and the retention period you need. What are you using to build APIs if i may ask?
escot 5y ago
The idea seems useful, although I don't consider it a pain point for myself necessarily. Between log mgmt and reporting I don't think I'm missing much. If you had to descirbe the single biggest feature treblle provides that something like sumologic doesn't, what would it be? Its not obvious that you can select different languages on this page: https://treblle.com/how-it-works https://treblle.com/how-it-works Bug -- I think you have a copy/paste issue because four of the links in the footer go to the same url (Features and Integrations both go to how-it-works). This is a run on sentence: > Understand who’s using your API, how they’re using it and how your API is responding in all those situations. If you have a minute to try my project knotend.com there's a top level comment, thanks.
- cindreta 5y ago
  Hi there, Vedran from Treblle. What do you use for log management and reporting? The biggest idea being Treblle is the ability for EVERYONE involved to see requests in real time in a format that is understandable to the average person in tech, not just a back-end developer. Most mobile developers can't read server logs nor they have access to servers that have them. Because we have access to every request we can compute things that you won't find it the logs: like request/endpoint documentation, location data, device information, app version, os version, server environment. More importantly you can literary search any request made to your API. So you can say something like: "Find all requests coming in from Las Vegas, to the Auth endpoint, from iOS withing the last 3 days". It can be even more granular. Also we actually generate and update your API documentation continuously including an OpenAPI Spec version. Thank you for your comments especially on the website we are working on it and on the redesign. We just got our seed round and we are looking to make things super polished so stay tuned. I would love to show you around Treblle if you want ping me at vedran@treblle.com

alek_m 5y ago

Looks good, congrats on the funding. I would love to see being implemented in more languages.

cindreta 5y ago
thank you very much! hope we get to help a lot of developers

throwaway123xxx 5y ago

I really like your website, qn: how did you make it? I can see how this would be useful as I'm building an API. The free tier is almost too generous and I think I'd be more inclined to pay for this if the free tier had about 1K free API calls and the smallest package was < $30 a month. May differ for others though. In terms of log retention, does anything prevent me from just replicating and storing the logs myself? If so log retention as feature differentiation is a bit superfluous imo. I think some of the features you offer could potentially be behind a paywall. Either way, looks really nice and I am considering being a customer when my team grows a bit more. Good luck!

cindreta 5y ago
Hi there i’m the founder of Treblle and also the guy who developed it all;) So the website itself is built using HTML/CSS/JS on the front-end and PHP/MYSQL/LARAVEL on the back-end. We didn’t use any fancy frameworks for the front-end because we managed to do what we want just with CSS. Plus it really helps with performance and loading times if you cut down on JS frameworks. To make sure it scales we use a lot of AWS services on top of Laravel Vapor. If you have any in depth questions about the tech stack let me know. Thank you for your comments! I am glad you would consider it. We originally had a 30 dollar package but thought that it might be to many options. We will adjust that based on your feedback :) When you say "replicating and storing the logs myself". It's not just about the RAW logs - it about who gets to see them and how. Because Treblle allows you to search those logs and say something like "Give me all requests for endpoint X withing a Y time frame that were made from New York, US". So yeah you could be logging thing to CloudWatch but it will just be logs who are not readable to the average person in my opinion. When you share a request from Treblle anybody can understand it, it's full of information that the original log doesn't have like the API version, device information, server information, location data and much more. Personally as a developer i also hate when you have to buy the biggest package just so you can get the feature you want. I find it sleazy. This way you literary pay for the requests and the retention period you need. What are you using to build APIs if i may ask?

escot 5y ago

The idea seems useful, although I don't consider it a pain point for myself necessarily. Between log mgmt and reporting I don't think I'm missing much. If you had to descirbe the single biggest feature treblle provides that something like sumologic doesn't, what would it be? Its not obvious that you can select different languages on this page: https://treblle.com/how-it-works https://treblle.com/how-it-works Bug -- I think you have a copy/paste issue because four of the links in the footer go to the same url (Features and Integrations both go to how-it-works). This is a run on sentence: > Understand who’s using your API, how they’re using it and how your API is responding in all those situations. If you have a minute to try my project knotend.com there's a top level comment, thanks.

cindreta 5y ago
Hi there, Vedran from Treblle. What do you use for log management and reporting? The biggest idea being Treblle is the ability for EVERYONE involved to see requests in real time in a format that is understandable to the average person in tech, not just a back-end developer. Most mobile developers can't read server logs nor they have access to servers that have them. Because we have access to every request we can compute things that you won't find it the logs: like request/endpoint documentation, location data, device information, app version, os version, server environment. More importantly you can literary search any request made to your API. So you can say something like: "Find all requests coming in from Las Vegas, to the Auth endpoint, from iOS withing the last 3 days". It can be even more granular. Also we actually generate and update your API documentation continuously including an OpenAPI Spec version. Thank you for your comments especially on the website we are working on it and on the redesign. We just got our seed round and we are looking to make things super polished so stay tuned. I would love to show you around Treblle if you want ping me at vedran@treblle.com