Skip to content

Conversation

weixiang1862
Copy link
Member

Fix unknown metadata in L2 aggregate worker

  • Add a unit test to verify that the fix works.
  • Explain briefly why the bug exists and how to fix it.
f3cfd891c8f14b25b96bdb1a7a2ae67c

L2 aggregate worker can't get metrics metadata because metadata is not serialized in grpc message, which will skip analysing of next workers(alarm, exporter) under oap cluster mode.

Comment on lines +296 to +298
if (metrics instanceof Meter) {
((Meter) metrics).initMeta(model.getName(), model.getScopeId());
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't remember other OAL metrics having this in serialization. Could you explain more about this issue?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#createNew should include initMeta logic already. I think the correct approach should be to use the correct serialization in RemoteServiceHandler, rather than here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend making RemoteHandleWorker handleWorker to provide an instance creator, and support OAL(new Object) and MAL(createNew) ways to initialize the object correctly.

@wu-sheng wu-sheng added bug Something isn't working and you are sure it's a bug! backend OAP backend related. labels Oct 14, 2025
@wu-sheng wu-sheng added this to the 10.3.0 milestone Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend OAP backend related. bug Something isn't working and you are sure it's a bug!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants