[chore] Update otelopscol to v0.159.0 by franciscovalentecastro · Pull Request #2388 · GoogleCloudPlatform/ops-agent

franciscovalentecastro · 2026-07-17T20:36:52Z

Description

Update otelopscol to v0.159.0 and fix some timestamp parsing bugs in 3rd party apps.

Details :

Added opt-in cpu labels : [receiver/hostmetrics/cpu] Make logical CPU attribute opt-in open-telemetry/opentelemetry-collector-contrib#49162
Disable newly on by default metric : [receiver/hostmetrics] Enable system.cpu.logical.count metric by default open-telemetry/opentelemetry-collector-contrib#49325
Added new possible values to mysql.commands metric : [receiver/mysql] Add DDL command types to mysql.commands metric open-telemetry/opentelemetry-collector-contrib#49863
Field verification was improved in : processor/metricstransform: add required-field validation for combine action open-telemetry/opentelemetry-collector-contrib#48919
Fixed timestamp parsing in some receivers.

Related issue

How has this been tested?

Checklist:

Unit tests
- Unit tests do not apply.
- Unit tests have been added/modified and passed for this PR.
Integration tests
- Integration tests do not apply.
- Integration tests have been added/modified and passed for this PR.
Documentation
- This PR introduces no user visible changes.
- This PR introduces user visible changes and the corresponding documentation change has been made.
Minor version bump
- This PR introduces no new features.
- This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
- This PR bumps the version.

quentinmit · 2026-07-20T19:59:44Z

 						Parser: confgenerator.ParserShared{
 							TimeKey:    "timestamp",
-							TimeFormat: "%Y-%m-%dT%H:%M:%S.%L",
+							TimeFormat: "%Y-%m-%dT%H:%M:%S.%LZ",


I think you want %z to parse this as UTC, or else it will be parsed as a local time, no?

Yes, you are right.

This also gives me insight that fluent-bit doesn't "fail to parse" a timestamp that has a "suffix" that is not within the described format. Being a bit more lenient that way.

quentinmit · 2026-07-20T21:21:32Z

 						Parser: confgenerator.ParserShared{
 							TimeKey:    "time",
-							TimeFormat: "%Y-%m-%d %H:%M:%S.%L %z",
+							TimeFormat: "%Y-%m-%d %H:%M:%S.%L %Z",


This is a fun one. strptime's %z is documented as "An RFC-822/ISO 8601 standard timezone specification. RFC-822 allows "UT" / "GMT" / "EST" / "EDT" / "CST" / "CDT" / "MST" / "MDT" / "PST" / "PDT" / 1ALPHA. ISO 8601 allows only Z or ±nn:nn. Notably absent from this list is UTC.

I added a test using UT, and glibc's strptime actually does not parse UT or GMT as valid %z specifiers.

So I'm convinced that %Z is indeed the correct specifier for these logs, and the fact that %z worked with Fluent Bit was a happy accident.

quentinmit · 2026-07-20T21:23:00Z

+	formattedTime := ottl.FormatTime(ottl.ToTime(v, "%Y-%m-%dT%T.%sZ"), "%Y-%m-%d %T.%s")
+	return v.Set(ottl.Concat([]ottl.Value{formattedTime, ottl.StringLiteral("+0000")}, " "))


Hm, is this guaranteed to actually produce a UTC time? Should we actually just be formatting with %z instead?

We were creating timestamps for Windows Event Logs using the output format "%Y-%m-%d %T.%s +0000", which i assume because the fluent-bit windows event logs were always using UTC in the format +0000.

I set %z (which translates to Golang Z0700) which generates Z instead. I think this is better. We could somehow hack the format to %z -> 0700 to get +0000 but it doesn't seem worth it.

The original PR (#1969) i assume was trying to replicate exactly what Windows Event Logs API returns (AFAIU, xml logs are stored always with UTC ¹ ) and how fluent-bit event logs timestamps are displayed.

Footnotes

https://superuser.com/questions/1531591/what-time-zone-does-windows-event-logs-show ↩

LujieDuan · 2026-08-07T19:19:20Z

fyi: found another issue with 0.156.0 that we will have to update: PR 2395 - Adding aggregation_type for combine

franciscovalentecastro · 2026-08-07T20:29:04Z

fyi: found another issue with 0.156.0 that we will have to update: PR 2395 - Adding aggregation_type for combine

Acknowledge! I was intending to update to 0.158.0 anyways. We can't update to 156 since it's missing the timestamp parsing fix. This PR hacks the fix, but it was released in 158.

…in couchbase.

…o change in OTel.

quentinmit reviewed Jul 20, 2026

View reviewed changes

franciscovalentecastro changed the title ~~[Draft] Update otelopscol to v0.156.0~~ [chore] Update otelopscol to v0.159.0 Aug 26, 2026

franciscovalentecastro force-pushed the fcovalente-otelopscol-v0.156.0 branch from f394007 to 23a4853 Compare August 26, 2026 15:19

quentinmit approved these changes Aug 26, 2026

View reviewed changes

franciscovalentecastro force-pushed the fcovalente-otelopscol-v0.156.0 branch from 7a2b046 to 0abaaeb Compare August 26, 2026 20:58

franciscovalentecastro and others added 23 commits August 27, 2026 16:47

Update otelopscol to v0.156.0.

6f92951

Update transformation tests.

b162070

Update submodule to quentinmit-strptime-L

9b6958f

Update transformation tests.

365aa66

Fix formatSystemTime by removing +0000 decimals from FormatTime.

37b90ff

Fix couchbase timestamp format.

5446c1c

Fix postgresql time format.

3142d02

Fix couchbase_goxdcr time format.

95c847a

Use %z instead of setting a literal +0000 string in the time format.

3a3aa7b

Use %z instead of a Z literal to parse correctly timezone offset …

1c39009

…in couchbase.

Revert goldens to keep PR small during review.

aef2321

Update formatSystemTime to use %z.

d704518

Revert confgenerator goldens to clean PR during review.

7cd0f6d

Update otelopscol to v0.159.0

f06a360

Fix goldens.

0999d1a

Don't attempt to set() a nil value. The semantics of this are about t…

8f123c1

…o change in OTel.

Fix __setif_value code to be appropriately nil-guarded

8a79082

Update goldens

6ab2ece

Add nil-guards to type conversion

5e8c653

Update goldens

8b88424

Update goldens.

df68e75

Set missing aggregation_type as sum in CombineMetrics.

ff8ab1a

Update cpu missing attributes in hostmetrics.

a14eddb

Add new possible values to "mysql.commands" metric.

495660b

franciscovalentecastro force-pushed the fcovalente-otelopscol-v0.156.0 branch from 92c9017 to 495660b Compare August 27, 2026 16:47

franciscovalentecastro added 2 commits August 27, 2026 18:53

Only keep labels for system.cpu.time metric.

9dbf901

Disable "system.cpu.logical.count" metric.

7705fd8

franciscovalentecastro merged commit 05c0f2f into master Aug 28, 2026
83 of 86 checks passed

franciscovalentecastro deleted the fcovalente-otelopscol-v0.156.0 branch August 28, 2026 15:07

Navigation Menu

Uh oh!

[chore] Update otelopscol to v0.159.0 - #2388

[chore] Update otelopscol to v0.159.0#2388
franciscovalentecastro merged 26 commits into
masterfrom
fcovalente-otelopscol-v0.156.0

franciscovalentecastro commented Jul 17, 2026 •

edited

Loading

Uh oh!

quentinmit Jul 20, 2026

Uh oh!

franciscovalentecastro Jul 20, 2026

Uh oh!

quentinmit Jul 20, 2026

Uh oh!

franciscovalentecastro Jul 20, 2026

Uh oh!

quentinmit Jul 20, 2026

Uh oh!

franciscovalentecastro Jul 20, 2026 •

edited

Loading

Uh oh!

LujieDuan commented Aug 7, 2026

Uh oh!

franciscovalentecastro commented Aug 7, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		formattedTime := ottl.FormatTime(ottl.ToTime(v, "%Y-%m-%dT%T.%sZ"), "%Y-%m-%d %T.%s")
		return v.Set(ottl.Concat([]ottl.Value{formattedTime, ottl.StringLiteral("+0000")}, " "))

Uh oh!

Conversation

franciscovalentecastro commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related issue

How has this been tested?

Checklist:

Uh oh!

quentinmit Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

franciscovalentecastro Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

quentinmit Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

franciscovalentecastro Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

quentinmit Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

franciscovalentecastro Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Footnotes

Uh oh!

LujieDuan commented Aug 7, 2026

Uh oh!

franciscovalentecastro commented Aug 7, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

franciscovalentecastro commented Jul 17, 2026 •

edited

Loading

franciscovalentecastro Jul 20, 2026 •

edited

Loading