opentracing-javascript

OpenTracing API for Javascript (both Node and browser). πŸ›‘ This library is DEPRECATED! https://github.com/opentracing/specification/issues/163 (by opentracing)

Opentracing-javascript Alternatives

Similar projects and alternatives to opentracing-javascript

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better opentracing-javascript alternative or higher similarity.

opentracing-javascript discussion

Log in or Post with

opentracing-javascript reviews and mentions

Posts with mentions or reviews of opentracing-javascript. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-17.
  • Kotlin Spring WebFlux, R2DBC and Redisson microservice in k8s πŸ‘‹βœ¨πŸ’«
    12 projects | dev.to | 17 Oct 2022
    Spring Spring web framework Spring WebFlux Reactive REST Services Spring Data R2DBC a specification to integrate SQL databases using reactive drivers Redisson Redis Java Client Zipkin open source, end-to-end distributed tracing Spring Cloud Sleuth auto-configuration for distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Kubernetes automating deployment, scaling, and management of containerized applications Docker and docker-compose Helm The package manager for Kubernetes Flywaydb for migrations
  • Go and ElasticSearch full-text search microservice in k8sπŸ‘‹βœ¨πŸ’«
    13 projects | dev.to | 16 Aug 2022
    Elasticsearch client for Go RabbitMQ Go RabbitMQ Client Library Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Echo web framework Kibana is user interface that lets you visualize your Elasticsearch Docker and docker-compose Kubernetes K8s Helm The package manager for Kubernetes
  • Go EventSourcing and CQRS with PostgreSQL, Kafka, MongoDB and ElasticSearch πŸ‘‹βœ¨πŸ’«
    16 projects | dev.to | 18 Jul 2022
    PostgeSQL as event store database Kafka as messages broker gRPC Go implementation of gRPC Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB MongoDB database Elasticsearch Elasticsearch client for Go. Echo web framework Kibana Kibana is data visualization dashboard software for Elasticsearch Migrate for migrations
  • OpenTelemetry vs OpenTracing - choosing one for instrumentation
    3 projects | dev.to | 28 Apr 2022
    OpenTracing was an open-source project aimed at providing vendor-neutral APIs and instrumentation for distributed tracing. In distributed cloud-native applications, it is difficult for engineering teams to see how requests are performing across services. And that’s where distributed tracing comes into the picture.
  • OpenTelemetry and Jaeger | Key concepts, features, and differences
    3 projects | dev.to | 9 Apr 2022
    OpenTracing is now archived, and it is suggested to migrate to OpenTelemetry.
  • Microservice communication Diagram
    1 project | /r/microservices | 27 Mar 2022
  • Go EventSourcing and CQRS microservice using EventStoreDB πŸ‘‹βš‘οΈπŸ’«
    12 projects | dev.to | 27 Feb 2022
    In this article let's try to create closer to real world Event Sourcing CQRS microservice using: πŸš€πŸ‘¨β€πŸ’»πŸ™Œ EventStoreDB The database built for Event Sourcing gRPC Go implementation of gRPC MongoDB Web and API based SMTP testing Elasticsearch Elasticsearch client for Go. Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus swag Swagger for Go Echo web framework Kibana Kibana is user interface that lets you visualize your Elasticsearch
  • Do Not Log
    1 project | news.ycombinator.com | 5 Jan 2022
    I agree; but I think it'll take years, if ever, to change this culture.

    Logging is a byproduct of a past time; everything is a file, stdout is a file, lets persist that file, now we have multiple replicas, lets collect the file into a multi-terabyte searchable database.

    The biggest downside: Its WILDLY expensive. Large orgs often have an entire team dedicated to maintaining logging (ELK) infrastructure. This price-tag inevitably leads to bikeshedding on backend teams about how to "reduce the amount we're logging" or "cleaning up the logs" or "structuring them to be more useful".

    Outside of development, they are so rarely useful. Yet inevitably someone will say: "you're just not structuring your logs correctly." Maybe that's true; similarly, I don't find vim to be a highly productive editing experience. Maybe I just don't have the thousands of extensions it would take to make it so. Or maybe You're stuck in the past and ignoring two decades of tooling improvement. Both can be true.

    I'm phrasing this as a false dichotomy, because in many teams: it is. Logging is easy; its built-in to most languages; so devs log. The information we need is in the system; its a needle in a haystack, but the needle is there. We log when a request comes in, when it hits pertinent functions, when its finished, how its finished, the manager says: "just look at the logs". Instead of "what better tooling can we make an investment in so future investigations of this nature don't take a full day."

    For starters: Tracing. Tracing systems should be built-in to EVERY LANGUAGE, just like console.log. We have a standard [1] sponsored by the Linux Foundation and supported by every major trace ingestion system. This is not a problem of camps and proprietary systems; its a problem of culture. I should be able to call a nodejs stdlib function at startup, specify where I want traces to go, sampling rate, etc, and immediately get every single function call instrumented. Its literally just highly-structured-by-default logging! Dump the spans to stdout by default! Our log ingestion systems can read each line, determine if its a span, if so route to trace ingestion, otherwise route to log ingestion.

    This is a critical step because it asserts that tracing is actually a very powerful tool that everyone needs to learn, like logging. Everyone knows about logging. Why? console.log. Its there, it gets used. Tracing right now is relegated to a subculture of "advanced diagnostics"; you gotta adopt a tracing provider, bring in dependencies, learn each implementation of OpenTracing, authenticate to send traces over HTTP... as a community, we should normalize just "dump traces like you dump logs, to stdout", have a formatter to make them nice to use in development, and now all that instrumentation work that any dev is capable of utilizing (just like console.log) "just works" in production.

    [1] https://opentracing.io/

  • I share my authentication server.
    18 projects | /r/golang | 20 Dec 2021
    Service mesh - ssup2ket services run on service mesh for detailed traffic control and easy monitoring. Service mesh is applied through Istio. Istio uses OpenTracing for easy request tracing between multiple services.
  • logging best practices
    1 project | /r/devops | 7 Dec 2021
  • A note from our sponsor - SurveyJS
    surveyjs.io | 13 Jun 2024
    With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more β†’

Stats

Basic opentracing-javascript repo stats
32
1,090
1.6
over 2 years ago

Sponsored
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io