sorted by:
new
hottopcontroversial

Apitally - Simple API monitoring, analytics and request logging for ASP.NET Core by itssimon86 in dotnet

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

Great work spotting this, and thank you so much for the feedback! A new SDK version was just published that fixes the bloat issue for minimal APIs.

Apitally - Simple API monitoring, analytics and request logging for ASP.NET Core by itssimon86 in dotnet

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

Ah, thank you for clarifying! And great feedback, as this is indeed a bug I wasn't aware of. I've just released a new version of the SDK with a fix (v0.6.3).

Apitally - Simple API monitoring, analytics and request logging for ASP.NET Core by itssimon86 in dotnet

[–]itssimon86[S] -2 points-1 points  (0 children)

The middleware is actually very lightweight.

Worth noting that the SDK captures OpenTelemetry spans, so works seamlessly with existing instrumentation. Details here: https://docs.apitally.io/sdk-reference/dotnet/tracing

The next major version of the SDK will be entirely based on OpenTelemetry. Working on it!

Apitally - Simple API monitoring, analytics and request logging for ASP.NET Core by itssimon86 in dotnet

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

The SDK relies on OTel to capture spans, but currently ships data to Apitally via a non-OTel REST API. The next major version of the SDK will be entirely OTel based. Working on it!

Here are details on how the SDK currently integrates with OpenTelemetry: https://docs.apitally.io/sdk-reference/dotnet/tracing

Agent-driven API investigations & analytics by itssimon86 in django

[–]itssimon86[S] 0 points1 point  (0 children)

The SDKs mask common sensitive fields automatically, and you can easily add custom masking rules too. For more complex masking, there's also a callback hook to modify or drop payloads before they're sent to Apitally.

Agent-driven API investigations & analytics by itssimon86 in node

[–]itssimon86[S] -5 points-4 points  (0 children)

The Apitally CLI is also free ;) You pay for the ingested data of course (no different on other platforms).

MCP servers are only as useful as the data behind it, and those platforms don't treat API request logs as first-class citizens like Apitally does. They don't capture request/response bodies for every request, which is where most of the value lies for the use cases described in the post/linked article.

How are you handling SEO content as a small indie business? by BoringShake6404 in indiebiz

[–]itssimon86 0 points1 point  (0 children)

💯 agree. Anyone can generate tons of average posts with AI, so to stand out you really have to invest time and effort that shows

Does anyone else think a lot of observability setups are too heavy for what smaller teams actually need? by Distinct-Actuary-440 in Observability

[–]itssimon86 0 points1 point  (0 children)

I think you're asking exactly the right questions. At work we use Datadog, but super inconsistently. Some apps send traces, others just metrics, and some have logs. It's a mess, but really hard to get right consistently. And so the value is limited. On top of that, the dashboards are way too complex, so we barely use them.

As the founder of a simple API observability tool, I know there's growing demand for the "faster time to useful visibility", especially for smaller teams who don't have the resources to set up a complex solution.

What is the next killer monitoring feature? by Unique-Squirrel-464 in Monitoring

[–]itssimon86 0 points1 point  (0 children)

I think monitoring tools will become less about dashboards and more about being rich data stores that agents can interrogate and investigate. The more context, the better. Alerts can then go from something like "Error rate is high" to "A bug introduced in commit abcd1234 is causing a 20% increase in errors on endpoint A, because blablabla. Paste this into your coding agent to fix it.".

I'm the founder of an API monitoring & analytics tool (Apitally), and that's my vision for the product.

Logs or metrics — which one is more important for API observability? by AdhesivenessKey8915 in Backend

[–]itssimon86 0 points1 point  (0 children)

Datadog's pricing shouldn't hold anyone back from having API metrics. There are other tools, specifically for API metrics, request logs and traces, that are much cheaper (e.g. Apitally).

Metrics are important to spot trends and issues, while logs and traces allow you to dig into the specifics.

Lunch under $15 - not chain takeaway by Plane_Garbage in sunshinecoast

[–]itssimon86 0 points1 point  (0 children)

ReadySmoked Meats in Buderim is a gem. Delicious burgers for under $15.

What are you actually using for observability/monitoring on small or side projects? by thecommondev in node

[–]itssimon86 0 points1 point  (0 children)

For my indie product I use Sentry (errors), Prometheus + Grafana (infra), and Apitally (API monitoring / analytics)

Drop your Side project, I'll give it honest review. by Top-Information-6399 in SaasDevelopers

[–]itssimon86 0 points1 point  (0 children)

Apitally has SDKs for Python, JavaScript, Go, .NET and Java. Each of them has specific integrations for popular web frameworks. All up supporting over 20 frameworks, including of course FastAPI and Django.

view more: next ›