Traces by hand: start_trace, tags and end state

start_trace and end_trace mark a trace around any code, with tags for filtering and an end state. As a context manager, the trace ends when the block does.

trace = agentops.start_trace("refund-ticket", tags=["refunds", "tier-1"])
decision = "approved"
agentops.end_trace(trace, end_state="Success")

with agentops.start_trace("parcel-ticket", tags=["delivery"]):
    pass

local_collector.flush()
for span in local_collector.SPANS:
    attributes = span["attributes"]
    print(span["name"], attributes.get("agentops.tags"), attributes.get("agentops.session.end_state"))

python manual.py

start_trace returns a trace context; end_trace takes it and an end_state, recorded on the root span. Tags, a list or a dictionary, are recorded as agentops.tags and are what the dashboard filters by: a customer, a product area, a release. The with form ended the second trace when the block finished, without an end state here because nothing set one.

Use manual traces where a decorator does not fit: a web request handler, a queue worker, a script with several phases.