# Semantic conventions lookup

Search the standard attribute names for services, HTTP, databases, messaging, errors and users.

## How it works

Using standard names means every tool understands your data the same way: dashboards, alerts and backends recognise http.route or db.system.name without mapping.

## Questions

### What if no standard name fits?

Use your own namespace, like acme.checkout.step, so it can’t clash with future standard names.

### Do older names still work?

Many backends accept both while conventions settle, but new code should use the current names.

## Related tools

- [Traceparent parser & generator](https://powertraces.com/tools/traceparent)
- [OpenTelemetry setup generator](https://powertraces.com/tools/opentelemetry-setup)
- [Collector config builder](https://powertraces.com/tools/collector-config)
- [OTLP JSON validator](https://powertraces.com/tools/otlp-json-validator)

[All tools](https://powertraces.com/tools)