[Robelkidin]

The problem is a developer spending time to set up alerts for their new feature. I have done it many times on splunk yet that is so inconvenient. it's limited to what the developer expects the error are. example setting up status code based alert on a feature. and what happens if error alerts. A developer has to manual trace logs for a bunch of traceID. LogClaw wants to solve this issue. LogClaw 24/7 monitors your logs no need to set up alerts. when error a rise it will create a ticket with all logs for a particular traceId. No spending time on splunk/datadog log dashboard. Besides that, most of incidents happen unplanned errors on production. Those planned ones a developer has already set up a graceful way of handling them. What happens if your feature works right, but it happens to be it used frequently and Out of memory, or database queries slows, or external api exhausted ...etc and causing the error. There are many unplanned errors that LogClaw will monitor. LogClaw injects all the logs so it knows what's happening through out your whole codebase.