Skip to content

FOUR-21032 Task Execution Time Metrics Collection #7874

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

Merged
merged 8 commits into from
Jan 17, 2025
Merged

Conversation

caleeli
Copy link
Contributor

@caleeli caleeli commented Jan 9, 2025

Task Execution Time Metrics Collection

Related Tickets & Packages

Code Review Checklist

  • I have pulled this code locally and tested it on my instance, along with any associated packages.
  • This code adheres to ProcessMaker Coding Guidelines.
  • This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
  • This solution fixes the bug reported in the original ticket.
  • This solution does not alter the expected output of a component in a way that would break existing Processes.
  • This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
  • This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
  • This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
  • This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:processmaker-bpmn-moddle:release-2024-fall

@caleeli caleeli requested a review from devmiguelangel January 9, 2025 23:45
@caleeli caleeli changed the base branch from epic/performance to release-2025-winter January 10, 2025 20:18
Copy link

gitguardian bot commented Jan 10, 2025

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@caleeli
Copy link
Contributor Author

caleeli commented Jan 14, 2025

This PR need to have merged Grafana, and Cache epics

@caleeli caleeli changed the base branch from release-2025-winter to epic/FOUR-20326_and_FOUR-20257 January 17, 2025 15:32
@caleeli caleeli changed the base branch from epic/FOUR-20326_and_FOUR-20257 to epic/FOUR-20326_and_FOUR-20257_and_FOUR-20327 January 17, 2025 15:48
@caleeli caleeli changed the base branch from epic/FOUR-20326_and_FOUR-20257_and_FOUR-20327 to epic/FOUR-20326_and_FOUR-20257_and_FOUR-20327_and_FOUR-20929 January 17, 2025 15:50
@caleeli caleeli changed the base branch from epic/FOUR-20326_and_FOUR-20257_and_FOUR-20327_and_FOUR-20929 to grafana-metrics January 17, 2025 15:57
@caleeli caleeli merged commit 9b044c4 into grafana-metrics Jan 17, 2025
2 of 3 checks passed
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