Asim Aslam
c7657f73f4
* test(harness): read agent plan from the scoped store
The store-scoping change moved an agent's plan from the default table
key agent/{name}/plan to its own table (database "agent", table {name},
key "plan"). The plan-delegate harness tests still read the old key and
failed with 'not found'; read through store.Scope(mem, "agent", name)
like the agent does.
* docs: orient agents-first across README, landing, and docs overview
Lead with agents (then services and flows), surface MCP + A2A as the
interop story, and frame agents as services. Landing hero and feature
grid reordered agents-first with an A2A gateway card.
* v6: module path go-micro.dev/v6, TLS secure by default, NewService
Cut v6. Three breaking changes, bundled so the major bump is paid once:
- Module path go-micro.dev/v5 -> go-micro.dev/v6 across all imports + go.mod.
- TLS verification on by default (was off). MICRO_TLS_SECURE removed;
MICRO_TLS_INSECURE=true opts out for self-signed/dev.
- micro.NewService(name, opts...) is the canonical service constructor,
symmetric with NewAgent/NewFlow; micro.New kept as a deprecated alias;
the old name-less NewService(opts...) removed. Generators emit NewService.
Also ports the JWT auth token provider in-module (go-micro.dev/v6/auth/jwt/token
on golang-jwt/jwt/v5), dropping the v5-pinned github.com/micro/plugins/v5/auth/jwt
and the deprecated dgrijalva/jwt-go.
Docs/README/landing updated to v6 and @latest; v5->v6 migration guide added;
CHANGELOG cut as [6.0.0]. Blog posts left at their historical versions.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Prometheus Wrapper
The prometheus wrapper package exposes standard request metrics (request
count, latency, errors) for go-micro services and clients, so they can be
scraped by a Prometheus server with zero extra boilerplate.
Resolves micro/go-micro#2893.
Installation
import prom "go-micro.dev/v5/wrapper/monitoring/prometheus"
Exported Metrics
All metrics are labelled with service, endpoint and status
("success" or "fail"). Labels are kept small on purpose to avoid
blowing up Prometheus memory.
| Metric | Type | Description |
|---|---|---|
micro_request_total |
Counter | Total number of requests handled. |
micro_request_duration_seconds |
Histogram | Request latency distribution (seconds). |
The micro prefix can be overridden with prom.ServiceName("myapp").
Basic Usage
import (
"go-micro.dev/v5"
prom "go-micro.dev/v5/wrapper/monitoring/prometheus"
)
func main() {
service := micro.NewService(
micro.Name("example.service"),
micro.WrapHandler(prom.NewHandlerWrapper()),
micro.WrapClient(prom.NewClientWrapper()),
micro.WrapSubscriber(prom.NewSubscriberWrapper()),
)
service.Init()
if err := service.Run(); err != nil {
panic(err)
}
}
To expose the metrics to Prometheus, serve the default promhttp handler
on a side HTTP endpoint:
import (
"net/http"
"github.com/prometheus/client_golang/prometheus/promhttp"
)
go func() {
http.Handle("/metrics", promhttp.Handler())
_ = http.ListenAndServe(":9100", nil)
}()
Then point Prometheus at it:
scrape_configs:
- job_name: 'example.service'
static_configs:
- targets: ['localhost:9100']
Wrappers
| Constructor | Wraps | Notes |
|---|---|---|
NewHandlerWrapper |
server.HandlerWrapper |
Incoming RPC handlers. |
NewSubscriberWrapper |
server.SubscriberWrapper |
Event subscribers (uses topic as endpoint). |
NewCallWrapper |
client.CallWrapper |
Outgoing unary RPC calls only. |
NewClientWrapper |
client.Wrapper |
Outgoing Call and Publish. |
NewClientWrapper is the right choice when you want metrics for both
Call and Publish; use NewCallWrapper if you only care about unary
calls and want lower overhead.
Configuration
All constructors accept functional options:
prom.NewHandlerWrapper(
prom.ServiceName("myapp"), // metric name prefix
prom.Namespace("prod"), // Prometheus namespace
prom.Subsystem("api"), // Prometheus subsystem
prom.ConstLabels(prometheus.Labels{"dc": "eu-1"}), // labels on every metric
prom.Buckets([]float64{0.005, 0.05, 0.5, 1, 5}), // latency buckets
prom.Registerer(myRegistry), // custom registerer
)
Defaults:
ServiceName:"micro"Buckets:prometheus.DefBucketsRegisterer:prometheus.DefaultRegisterer
Reusing Collectors
Creating multiple wrappers with the same options (e.g. NewHandlerWrapper
and NewClientWrapper together) is safe: the collectors are cached per
(name, namespace, subsystem) triple and AlreadyRegisteredError from
Prometheus is handled transparently, so the existing collector is reused.
Testing
The package ships with unit tests that use a fresh prometheus.Registry
per test to keep assertions isolated:
go test ./wrapper/monitoring/prometheus/...
License
Apache 2.0