Absolutely agreed! The end-to-end governance across different layers is what we offer to enterprises as a part of the enterprise-first Guard0 Platform. And as you rightly pointed out, access is one of the loose ends in many of the places because it always has been a loosely defined thing at the loss of places. Our thesis is to control and govern access, behavior, and actions. Would you mind opening an issue with specific details or the problem? I believe the g0 scan and g0 test should capture the credential issue, but if not, we can add the desired functionality.
Yeah! You can do it with Jaeger or Hypertrace. Hypertrace in this case will provide you more entity focused view so you can see dedicated dashboards for your APIs, services and backends.
Identifying expensive method calls is very easy with Hypertrace due to OOB metrics and additional enrichment which happens in ingestion pipeline. Many of our users are using Hypertrace for very similar use-case.
When compared to Jaeger, Hypertrace gives you API first and entity focused view. Which means, You can see list of API's in your system, slice and dice on various attributes in your API traces, you can also do similar for Services and backends.
There's dedicated dashboard for every service, API and backend which gives you metrics like latency, calls, error rate along with health radar.
And did I even started talking about explorer? It let's you slice and dice on your trace data as well as span data and also provides you real-time visualizations.
Hypertrace has a richer and more enterprise level functionality when it comes to Distributed tracing. We are adding more features as we are talking including alerting, application metrics support which makes it more of an API Observability tool which can satisfy more wider range of use-cases.
The community license may require clarification. It says the following: For example, it does not allow hosting of Hypertrace Metrics, Application Flow, Advanced Slice & Dice or other software licensed under the Traceable Community License as online service offerings that compete with Traceable SaaS products or services that provide the same software. If you are not doing what is excluded, this license will not affect you.
The part "Traceable SaaS products or services that provide the same software" seems deceptively simple yet it's vague. My interpretation would be the following: if I operate a PaaS, regardless of the primary function of this PaaS, where tracing plays a complimentary role, stay away from CL items as any platform with Hypertrace in it "provides same software".
Yup, your interpretation is correct. Basically, if you want to use Community edition for internal purpose at your organization, it's completely available but you can't sell a product built on top of Hypertrace which will compete with any Traceable SaaS product, in any way.
