Skip to content

go collector: add fips140ems runtime metric - #2092

Closed
wieghx wants to merge 2 commits into
prometheus:mainfrom
wieghx:feat/go-collector-fips140ems
Closed

go collector: add fips140ems runtime metric#2092
wieghx wants to merge 2 commits into
prometheus:mainfrom
wieghx:feat/go-collector-fips140ems

Conversation

@wieghx

@wieghx wieghx commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

What

Regenerate the Go collector expected-metric lists for Go 1.25 and 1.26 so they include the new runtime metric:

/godebug/non-default-behavior/fips140ems:events
go_godebug_non_default_behavior_fips140ems_events_total

Files were produced with the existing generators:

  • go run prometheus/gen_go_collector_metrics_set.go go1.26.6
  • go run prometheus/collectors/gen_go_collector_set.go go1.26.6
  • same pair with go1.25.13 (what actions/setup-go currently installs for 1.25 with check-latest: true)

Why

main Test has been red since 2026-08-17 (run 32022436024) with:

found new runtime/metrics metric /godebug/non-default-behavior/fips140ems:events

This is separate from #2091 (GatherAndFormat).

How to verify

go test ./prometheus/ ./prometheus/collectors/ -count=1

Also checked with go1.25.13.

cc @bwplotka

This PR was written in part with the assistance of generative AI.

Go 1.25.13 and 1.26 expose
/godebug/non-default-behavior/fips140ems:events. Regenerate the
expected metric lists so Test and collectors allow-list tests pass
on current CI toolchains.

Signed-off-by: wieghx <gudemail1991@gmail.com>
Signed-off-by: wieghx <gudemail1991@gmail.com>
@bwplotka

Copy link
Copy Markdown
Member

I think this was already done, no? #2090

@wieghx

wieghx commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

You're right — #2090 already regenerated the runtime metric allow-list, including fips140ems. Closing this as a duplicate.

@wieghx wieghx closed this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants