Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add actor metrics #9294

Merged
merged 3 commits into from
May 5, 2022
Merged

Add actor metrics #9294

merged 3 commits into from
May 5, 2022

Conversation

Zelldon
Copy link
Member

@Zelldon Zelldon commented May 5, 2022

Description

As discussed here https://camunda.slack.com/archives/C037RS2JHB8/p1651668160788749 add new actor metrics but no new panels for now.

Details:

  • Add counter for actorTask execution
  • Add histogram to observe actorTask execution

Currently starting a benchmark to verify whether metrics are exported as expected.

I will create a separate PR for the atomix executors.

@npepinpe I'm not sure whether it fulfills all requirements for #9282 I will remove my assignment then.

Related issues

related #9282

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually
  • The change has been verified by a QA run
  • The impact of the changes is verified by a benchmark

Documentation:

  • The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
  • New content is added to the release announcement
  • If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

Add counter for actorTask execution
Add histogram to observe actorTask execution
@Zelldon
Copy link
Member Author

Zelldon commented May 5, 2022

Seems to work. Example panels people could create

metrics

Copy link
Member

@npepinpe npepinpe left a comment

Choose a reason for hiding this comment

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

🚀 No blockers, but please check the comments

import io.prometheus.client.Counter;
import io.prometheus.client.Histogram;

public class ActorMetrics {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
public class ActorMetrics {
final class ActorMetrics {

Copy link
Member

Choose a reason for hiding this comment

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

🔧 As a rule of thumb, I would generally keep the lowest visibility required if only to make sure when other classes depend on one (i.e. it must be made public) hopefully we think about it and what it means to couple them.

Copy link
Member Author

@Zelldon Zelldon May 5, 2022

Choose a reason for hiding this comment

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

I guess I shouldn't just copy old branches 😅 BTW why we still have no check for class needs to be final ? 🤔 I guess it is not easy to detect ? 🤔 Or what is the reason?

@Zelldon
Copy link
Member Author

Zelldon commented May 5, 2022

bors r+

@zeebe-bors-camunda
Copy link
Contributor

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.

None yet

2 participants