FOUR-20257 - Grafana

[gproly]

Feature

Establish Grafana APM Pattern/Mechanism

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-20257

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14796648	Triggered	Generic Password	5a10ad0	metrics/compose.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}

[processmaker-sonarqube]

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

[boliviacoca]

@gproly please try removing the commit that has the SEC observation or skip it, so this is no longer an observation. Keep in mind that Engines needs to have this one merged as base.
Thanks

CC: @nolanpro , @ryancooley , @caleeli

[nolanpro]

@gproly please try removing the commit that has the SEC observation or skip it, so this is no longer an observation. Keep in mind that Engines needs to have this one merged as base. Thanks

CC: @nolanpro , @ryancooley , @caleeli

@boliviacoca The issue was fixed but I don't have access to Git Guardian to go in and skip it. It can be safely ignored.

[nolanpro]

These changes have been merged into #7913