Description:
$subject

Related Issues:
#132

Description:
Currently the grafana dashboard includes graphs for many categories (HTTP Client, HTTP Service, SQL Client). But sometimes, some categories won't have any data to show. We need to organize the dashboard as well as include some other categories.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
As a hyatt demo preparation, we need to create a dashboard for Ballerina Metrics observation in Datadog.
Intially we need to include the graphs that we have already included in Grafana.

As a first step, we can include HTTP Service Metrics and HTTP Client Metrics which are being most frequently used.
Later, we can include SQL Metrics and Graphql Metrics.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
For wso2 con 24, ballerina team presents a graphql service demo with observability. We need to create a custom dashboard visualizing GraphQL service related metrics.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Current Grafana dashboard for metrics observation is outdated and it needs to be updated.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Ballerina System Metrics has been removed with b25a9b4
Need to add it back once the BVM starts publishing the metrics

I've got the following warning when using this module.

HINT [ballerinax/prometheus/0.2.0::metric_reporter.bal:(63:13,63:13)] concurrent calls will not be made to this method since the method is not an 'isolated' method

This seems to be a blocker for performance.

Description:
A workflow should be added to verify graalvm compatibility for prometheus module.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Following occurs when datadog is configured to fetch from the Ballerina metrics endpoint.

2024-06-12 23:20:14 +0530 | CORE | ERROR | (pkg/collector/worker/check_logger.go:71 in Error) | check:openmetrics | Error running check: [{"message": "There was an error scraping endpoint http://localhost:9797/metrics: 406 Client Error: Not Acceptable for url: http://localhost:9797/metrics", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python3.11/site-packages/datadog_checks/base/checks/base.py\", line 1224, in run\n    self.check(instance)\n  File \"/opt/datadog-agent/embedded/lib/python3.11/site-packages/datadog_checks/base/checks/openmetrics/v2/base.py\", line 78, in check\n    raise_from(type(e)(\"There was an error scraping endpoint {}: {}\".format(endpoint, e)), None)\n  File \"<string>\", line 3, in raise_from\nrequests.exceptions.HTTPError: There was an error scraping endpoint http://localhost:9797/metrics: 406 Client Error: Not Acceptable for url: http://localhost:9797/metrics\n"}]

Description:
Currently coverage numbers are not properly getting captures due to ballerina sources are being testing using Java unit tests. Proper approach is to migrate tests using Testerina and running using it.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
While updating the Observability implementation for Ballerina SLP8, we have made several changes to the generated metrics. However, Grafana dashboard had not yet been updated to reflect these changes. This needs to be updated.

Dashboard: https://github.com/ballerina-platform/module-ballerinax-prometheus/blob/main/grafana-dashboard.json

Affected Product Version:
Ballerina SLP8

Description:
I recently tried out metrics monitoring with prometheus and grafana as mentioned ballerina website. When I import and view the grafana dashboard, In progress request count was always negative and the negative value kept on increasing as I send more requests to the underlying ballerina service.

This needs to be fixed soon since this is the most visible metric in the grafana dashboard.

Affected Product Version:
SL Beta 4

Steps to reproduce:
See description

Description:
Create central publish workflow as in other ballerinax repositories (ex: - https://github.com/ballerina-platform/module-ballerinax-mysql/blob/master/.github/workflows/central-publish.yml)

Description:
Grafana dashboard queries use min_over_time, max_over_time to get the difference of a range vector to produce outputs such as req/min, errors/min. This breaks at the initial phase as the minimum and maximum of the initial query execution is the same.

But this issue resolves as the time flows because in the next 1 minute period there are min max values.

eg :
sum(max_over_time(requests_total_value{instance=~"$instance",protocol=~"$protocol",http_method=~"$http_method",http_url=~"$http_url",service=~"$service",resource=~"$resource",connector_name="http"}[1m])-min_over_time(requests_total_value{instance=~"$instance",protocol=~"$protocol",http_method=~"$http_method",http_url=~"$http_url",service=~"$service",resource=~"$resource",connector_name="http"}[1m]))

Sugeestions

Instead of using min,max of a range vector use the rate function to calculate the
floor( sum(rate(requests_total_value{connector_name="http"}[1m])*60))

Description:
When we try to build ballerina native executable jar with including jaeger, it gives some runtime errors. We need to add configurations to resolve those errors.