Synthetic Monitoring with the Tracetest GitHub Action

This page summarizes the projects mentioned and recommended in the original post on

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
  • tracetest-github-action

    GitHub Action for running trace-based tests against Tracetest with our CI/CD pipeline

  • In this article, I’ve explained how the Tracetest team uses synthetic monitoring to evaluate the Tracetest open beta using GitHub Actions using Tracetest’s new GitHub Action to configure GitHub Workflows. With these tools, our team can add more monitoring to Tracetest and validate that our systems are working as expected. You’re now fully equipped to implement this knowledge in your own GitHub Actions to trigger trace-based tests easily!

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • tracetest

    🔭 Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.

  • It’s official! You can now use synthetic monitoring to run trace-based tests with Tracetest’s new GitHub Action. I’ve already implemented dogfooding and it’s currently running in production as health checks, running hourly, here.

  • opentelemetry-demo

    This repository contains the OpenTelemetry Astronomy Shop, a microservice-based distributed system intended to illustrate the implementation of OpenTelemetry in a near real-world environment.

  • # test suite based on 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

  • slack-github-action

    Send data into Slack using this GitHub Action!

  • As a final step, you can add a notification step that tell you if the tests failed. To do that, I'm using slackapi/slack-github-action that allows you to send a Slack message about the test conclusion. In my case, I've set it to send messages only in case of failures:

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Demystifying Observability 2.0

    2 projects | | 10 Jun 2024
  • Implementing OTel Trace Context Propagation Through Message Brokers with Go

    4 projects | | 4 Apr 2024
  • Setup and Teardown of Tracetest Tests with Test Suites

    2 projects | | 21 Feb 2024
  • Automating Tracetest Tests via Typescript or Javascript

    1 project | | 21 Feb 2024
  • Sumo Logic and Tracetest: AI-Driven Observability Meets Testing

    2 projects | | 18 Jan 2024