opentelemetry-dotnet
Elasticsearch
opentelemetry-dotnet | Elasticsearch | |
---|---|---|
7 | 91 | |
2,968 | 67,632 | |
1.2% | 0.6% | |
9.7 | 10.0 | |
5 days ago | 7 days ago | |
C# | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opentelemetry-dotnet
-
ASP.NET Core: Monitoreo con OpenTelemetry y Grafana
open-telemetry/opentelemetry-dotnet: The OpenTelemetry .NET Client (github.com)
-
Guide to Distributed Tracing with OpenTelemetry Dotnet
💡Good to know -- If you wish to export traces to Jaeger, you should use the AddJaegerExporter instead of the AddOtlpExporter. Visit the opentelemetry-dotnet repository to see how it's done.
-
Observability with Grafana Cloud and OpenTelemetry in .net microservices
We're going to use OpenTelemetry .NET SDK. Add following nuget dependencies to the project:
-
OpenTelemetry in Action: Identifying Database Dependencies
We instrument the application with the OpenTelemetry SDK and SqlClient instrumentation library for .NET. First, we add the following NuGet package references to the API’s project file:
-
State for each API Request
It should be handled automatically by OpenTelemetry middlewares. Just look through documentation and samples https://github.com/open-telemetry/opentelemetry-dotnet
-
[c#] Using W3C Trace Context standard in distributed tracing
Besides that, the propagation fields (traceparent and tracestate) were added in the message header. In the last article, I said that the standard (in the Working Draft (WD) step of the w3c process) recommends to add the propagation fields in the application-properties section by the message publisher. For the current example, I chose to propagate that context in the message header even for AMQP calls as was done in the dotnet OpenTelemetry example. It's important to reinforce that Trace Context: AMQP protocol is not a W3C Recommendation yet. Take a look at the place where the propagation fields were added:
-
Tracing End-to-End Data from Power Apps to Azure Cosmos DB
As long as the Azure Functions app knows the instrumentation key from an Application Insights instance, it traces almost everything. OpenTelemetry.NET is one of the Open Telemetry implementations, has recently released v1.0 for tracing. Both metrics and logging are close to GA. However, it doesn't work well with Azure Functions. Therefore, in this post, let's manually implement the tracing at the log level, which is sent to Application Insights.
Elasticsearch
-
Elasticsearch Version 9
You could check out their GitHub and see what is going on https://github.com/elastic/elasticsearch/issues
- One .gitignore to rule them all
-
Who's hiring developer advocates? (October 2023)
Link to GitHub -->
-
Do we think about vector dbs wrong?
I believe the 1024 limit has been upped in recent versions of Elasticsearch
https://github.com/elastic/elasticsearch/issues/92458
-
Elasticsearch VS openobserve - a user suggested alternative
2 projects | 30 Aug 2023
- A dedicated Elasticsearch query language (ES|QL)
- Fleet datastreams: custom index templates
-
Integrating Elasticsearch with Node.js Applications
Elasticsearch is written in Java and its source code is available on Github.
-
Murmur3 hash plugin for nested objects?
I don't think the murmur3 hash implementation has changed since it was added as the default in version 2.0 (see the [changes](https://github.com/elastic/elasticsearch/commits/main/server/src/main/java/org/elasticsearch/cluster/routing/Murmur3HashFunction.java)). The plugin itself has seen [more changes](https://github.com/elastic/elasticsearch/commits/main/plugins/mapper-murmur3) but that's IMO because of internals and not visible changes in the calculations.
-
Mongo or Mysql for 10tb of JSON documents, I'm questioning my previous choice.
Mysql is not as open source as postgres (long story). And you can see how open elasticsearch is by just having access to the bugs database https://github.com/elastic/elasticsearch/issue
What are some alternatives?
ApplicationInsights-dotnet - ApplicationInsights-dotnet
OpenSearch - 🔎 Open source distributed and RESTful search engine.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Apache Superset - Apache Superset is a Data Visualization and Data Exploration Platform [Moved to: https://github.com/apache/superset]
zipkin - Zipkin is a distributed tracing system
bleve - A modern text/numeric/geo-spatial/vector indexing library for go
C# StatsD Client
pgvector - Open-source vector similarity search for Postgres
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Whoosh
trace-context-w3c - W3C Trace Context purpose of and what kind of problem it came to solve.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow