open-meteo
opentelemetry-dotnet
open-meteo | opentelemetry-dotnet | |
---|---|---|
46 | 7 | |
2,006 | 3,001 | |
8.0% | 2.3% | |
9.7 | 9.7 | |
3 days ago | 2 days ago | |
Swift | C# | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
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.
open-meteo
- Open-Meteo Free Weather API
-
Show HN: The Astro App
Yup, just manually type your location in that window.
Weather is coming (at least for now) from https://open-meteo.com/
-
(Back to) omWeather as the bundled weather app in CalyxOS?
I tried out the new omWeather and I definitely like it even better now. It uses a different data source, open-meteo.com, which doesn't require an API key the way OpenWeatherMap does, has better location search, has working sunrise/sunset time display, and a more informative main screen widget with observation and forecast information.
- Open-Meteo: an open-source weather API
-
Creating a simple wind forecast bot in Mastodon
Then I started to learn about wind and I got interested in getting wind details easily so to note them down. I asked around my community and I got an answer: open-meteo.
- Open-Meteo: FOSS weather API partnered with national weather services
-
Open-Meteo Weather API integration + Free Icons + Free Widgets
Open-Meteo
- ASP.NET Core: Monitoreo con OpenTelemetry y Grafana
-
Bee
We used free and open-source weather API Open Meteo to get a real-time forecast and convert data such as windspeed into the Beaufort scale for surveying.
-
How to hide API key?
I ran into this exact problem almost a year ago now when I first started learning. Simple answer is you can’t unless you build your own server and use environment variables. My solution was to use an API that doesn’t need a key.
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.
What are some alternatives?
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.
ApplicationInsights-dotnet - ApplicationInsights-dotnet
esphome - ESPHome is a system to control your ESP8266/ESP32 by simple yet powerful configuration files and control them remotely through Home Automation systems.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
ultra-weather - UltraWeather gives user-friendly, actionable weather forecasts.
zipkin - Zipkin is a distributed tracing system
remote_homeassistant - Links multiple home-assistant instances together
C# StatsD Client
appdaemon - :page_facing_up: Python Apps for Home Automation
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
yr-weather-symbols - Weather symbols for yr.no
trace-context-w3c - W3C Trace Context purpose of and what kind of problem it came to solve.