llama-stack-mirror/llama_stack/providers/inline/agents/meta_reference
Charlie Doern f22aaef42f
chore!: remove telemetry API usage (#3815)
# What does this PR do?

remove telemetry as a providable API from the codebase. This includes
removing it from generated distributions but also the provider registry,
the router, etc

since `setup_logger` is tied pretty strictly to `Api.telemetry` being in
impls we still need an "instantiated provider" in our implementations.
However it should not be auto-routed or provided. So in
validate_and_prepare_providers (called from resolve_impls) I made it so
that if run_config.telemetry.enabled, we set up the meta-reference
"provider" internally to be used so that log_event will work when
called.

This is the neatest way I think we can remove telemetry from the
provider configs but also not need to rip apart the whole "telemetry is
a provider" logic just yet, but we can do it internally later without
disrupting users.

so telemetry is removed from the registry such that if a user puts
`telemetry:` as an API in their build/run config it will err out, but
can still be used by us internally as we go through this transition.


relates to #3806

Signed-off-by: Charlie Doern <cdoern@redhat.com>
2025-10-16 10:39:32 -07:00
..
responses fix(responses): fixes, re-record tests (#3820) 2025-10-15 16:37:42 -07:00
__init__.py chore!: remove telemetry API usage (#3815) 2025-10-16 10:39:32 -07:00
agent_instance.py feat(api)!: BREAKING CHANGE: support passing extra_body through to providers (#3777) 2025-10-10 16:21:44 -07:00
agents.py feat: Add responses and safety impl extra_body (#3781) 2025-10-15 15:01:37 -07:00
config.py feat: add list responses API (#2233) 2025-05-23 13:16:48 -07:00
persistence.py refactor(logging): rename llama_stack logger categories (#3065) 2025-08-21 17:31:04 -07:00
safety.py refactor(logging): rename llama_stack logger categories (#3065) 2025-08-21 17:31:04 -07:00