opentelemetry-demo
dotenv
Our great sponsors
opentelemetry-demo | dotenv | |
---|---|---|
18 | 219 | |
1,416 | 18,473 | |
7.4% | - | |
9.5 | 9.0 | |
5 days ago | about 2 months ago | |
TypeScript | JavaScript | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
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-demo
-
Implementing OTel Trace Context Propagation Through Message Brokers with Go
Here is a typical trace from the OpenTelemetry demo project.
-
Synthetic Monitoring with the Tracetest GitHub Action
# test suite based on https://github.com/open-telemetry/opentelemetry-demo/tree/main/test/tracetesting/frontend-service type: Test spec: id: frontend-view-cart name: 'Frontend: View cart' description: Simulate a user viewing the shopping cart trigger: type: http httpRequest: url: http://${var:FRONTEND_ADDR}/api/cart?userId=2491f868-88f1-4345-8836-d5d8511a9f83 method: GET headers: - key: Content-Type value: application/json specs: - name: It called the frontend with success selector: span[tracetest.span.type="general" name="Tracetest trigger"] assertions: - attr:tracetest.response.status = 200 - name: It retrieved the cart items correctly selector: span[name="oteldemo.CartService/GetCart"] assertions: - attr:rpc.grpc.status_code = 0
-
The Power of Traces: Learn by Contributing to OpenTelemetry
Contributing to the OpenTelemetry Demo is a great way to get involved and showcase your skills in the OpenTelemetry community. It's a real-world example of OpenTelemetry in action, and by actively contributing, you enhance your understanding and improve the project's quality.
-
Tracetest Monthly Newsletter - July 2023
Trace-based testing added to OpenTelemetry Demo
-
Hands-on OpenTelemetry: Troubleshoot issues with your instrumented apps
Examples and the tutorial in this blog post use the OpenTelemetry Astronomy Shop Demo to show what you can do with OpenTelemetry and New Relic. This application is built and maintained by the OpenTelemetry open-source community, and it provides a real-world example of a distributed application that’s been instrumented with OpenTelemetry. In the Deploying the OpenTelemetry Astronomy Shop demo app section, you’ll have an opportunity to get hands-on experience spinning up your own version of this application. You’ll learn how to:
-
Looking for resources to learn Kubernetes at a deep level.
Take this https://github.com/open-telemetry/opentelemetry-demo
-
2 Years Solution Engineer Experience + 1 Support Engineering, Would my background fit moving into SRE?
I mean, you really just need experience instrumenting apps and tinkering with them to play with OTEL. https://github.com/open-telemetry/opentelemetry-demo is a good start. You can modify the collector to point to any backend of your choice.
-
Tracetest in Action: Running Trace-Based Tests on the OpenTelemetry Demo App with Nomad
I got to play around with these newer features last December, after a months-long hiatus, and it was really cool to see the evolution of the product. If you follow my work, you’ll know that I play in both the Kubernetes and Nomad worlds. Today, I’ll be taking you on a quick little guided tour of Tracetest, using Traces from the OpenTelemetry Demo App to give you a feel for how it works. The whole setup will be running on HashiCorp Nomad. \
-
Chaining API Tests to Handle Complex Distributed System Testing
By having an observability infrastructure gather information about a set of API/microservices, we can have a concise view of the operation of these services and start thinking in an observability-driven way to test your software. Tracetest can help. When given an API endpoint, Tracetest checks observability traces to see if this API is behaving as intended. For example, let’s try to test an OpenTelemetry Astronomy Store which has the exact same use cases that we want to check. To test the "Add product to the shopping cart" task, we can create a test, define a URL and payload in the trigger section that we send to the Cart API and use the specs to define our assertions, checking if the API was called with the correct Product ID and if this product was persisted correctly.
-
How to Convert Kubernetes Manifests into Nomad Jobspecs
In my latest Nomadification Project (TM), I got the OpenTelemetry Demo App to run on Nomad (with HashiQube, of course). To do this, I used the OpenTelemetry Demo App Helm Chart as my guide. In doing this, and other Nomadifications, I realized that I’ve never gone through the process of explaining the conversion process from Kubernetes manifests to Nomad jobspecs.
dotenv
-
Tutorial: React + Emailjs
We will put our Emailjs environment variables in a dotenv (.env) file. To read more about the purpose of this file click here.
-
How to Use Environment Variables in Node.js
Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.
-
Extracting YouTube video data with OpenAI and LangChain
dotenv: Designed to load environment variables from a .env file into the process.env environment
-
Top Secrets Management Tools for 2024
Like Doppler, Infisical uses environment variable injection. Similar to the Dotenv package for Node, when used in Node, it injects them at run time into the process object of the running app so they're not readable by any other processes or users. They can still be revealed by a crash dump or logging, so that is a caveat to consider in your code and build scripts.
- AI for Web Devs: Your First API Request to OpenAI
-
An intro to Appwrite | Building a To-do list with SvelteKit
We'll be working with databases' ids and different info that should be secured so I would advise you to create a .env file to store said info. We'll do this by installing dotenv into our project and use it accordingly:
-
Building and deploying AI agents with E2B
dotenv - For reading our API keys from the environment
-
A decade of dotenv
As an avid dotenv user I wanted to thank their maintainers for keeping the project alive for 10 years (wow). A perfect exemplary of dedication to Open Source.
-
Automate Your Way to Faster Deployments: CI/CD for MERN Apps
Sensitive data like database URLs, API keys, and passwords should never be hardcoded in your application code. Instead, use environment variables accessed at runtime to keep this information secret. Popular dotenv libraries like dotenv make this easy for Node.js apps.
- Servidor para Blog, com Autenticação JWT - Node.Js & Mysql
What are some alternatives?
hypertrace - An open source distributed tracing & observability platform
cross-env
nomad-conversions - Repo containing conversions of Kubernetes and/or Docker Compose apps to Nomad jobspecs
multiline
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
hashiqube - HashiQube - All the Hashicorp products in a Container or VM for anyone to demo or practise with.
hardhat-deploy - hardhat deployment plugin
Eliot - Eliot: the logging system that tells you *why* it happened
fastify - Fast and low overhead web framework, for Node.js
unified-observability-k8s-kubecon - Unified Observability for Kubernetes at KubeCon NA '22
Visual Studio Code - Public documentation for Visual Studio Code