Skip to main content
Tero discovers services from your integrations. Each one becomes a hub in the context graph, owning log events, trace spans, and metrics, and relating to other services through dependencies.

​
What Tero knows

Tero doesn’t just import names. It analyzes logs and traces to understand what each service does, what technologies it uses, and how it relates to other services.

​
Exploring a service

Open any service to see what Tero figured out: description, technologies, dependencies, failure scenarios, and log events. Everything connected to that service in the graph.

​
Using in chat

Reference a service with @ to scope your questions: 
@checkout why are we seeing elevated error rates?
@payment what are the common failure modes?
@kafka what log events does this produce?
Tero pulls in everything connected: the service’s description, dependencies, failure scenarios, log events. Your question gets answered in that full context.

​
Improving context

Tero generates descriptions and infers technologies, but you can refine what it knows:
  • Edit descriptions to add detail Tero couldn’t infer
  • Add failure scenarios your team knows about
  • Note ownership so Tero knows who to reference
The more you refine, the better Tero’s answers become.