FOUR-20540 Validation and Documentation-part 1

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.

[gproly]

Validation and Documentation-part 1

Validate Metrics Setup:

• Refer to FOUR-19547: Task Metrics Triage for examples and ensure metrics align with project goals.
• Use the setup as a reference for monitoring Laravel application performance.

Create Documentation:

• In the README.md of your project, create a Metrics section:

Related Tickets & Packages

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

[nolanpro]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gproly]

@gproly

• We don't need the "Using PromPHP/prometheus_client_php in Laravel with a Facade" section. Please remove it. Instead, please give some examples how developers can use the Metrics facade from here: FOUR-20535 Initial Setup (Laravel + Prometheus Integration) #7772
• I think it still needs to be easier for developers to view Grafana. Create a folder in core called metrics and use Docker Compose. Use this as an example: https://github.com/docker/awesome-compose/tree/master/prometheus-grafana

The developer should only need to cd metrics and docker compose up then visit http://localhost:3000 to see Grafana

These changes will be introduced in the feature/FOUR-20535 branch due to a dependency on changes. Therefore, this branch and the pull request are being closed.