Skip to main content

Observability: Configurable service name for check or check group

Feature RequestTracesObservability

When creating the root span, checkly uses the service name checkly to make it very obvious that it’s the one we originate that comes through with the Check requests.

It’d be nice to make this service name configurable to identify trends across applications or to have them grouped correctly in 3rd party services such as Honeycomb, which uses the service name to select the dataset spans get aggregated to.

Posted by María de Antón ·
2 comments

Log in to comment and vote

Comments2

  • esara

    •

    Jan 14, 2025

    As a client trace, the server.address or peer.service  is supposed to be the service that is accessed by checkly check instead of the string “checkly”, which does not help much. https://opentelemetry.io/docs/specs/semconv/general/attributes/#serveraddress or  https://opentelemetry.io/docs/specs/semconv/attributes-registry/peer/
    One of the possibilty is to extract the hostname from the check, it is reasonable to assume that is the service (with the same servicename captured by honeycomb and others on the server side)

    • María de Antón

      •

      Jan 22, 2025

      Thank you, @esara! That’s an idea that we had not considered, but would definitely work as the default one that people could then override. We are keeping this in our roadmap for when we get here.