-
Notifications
You must be signed in to change notification settings - Fork 25
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
NETOBSERV-1343: generate dashboards from metrics API #609
Conversation
@jotak: This pull request references NETOBSERV-1343 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
Pending to do:
|
7d96d0f
to
a40f093
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #609 +/- ##
==========================================
+ Coverage 66.35% 67.03% +0.68%
==========================================
Files 65 66 +1
Lines 7321 7557 +236
==========================================
+ Hits 4858 5066 +208
- Misses 2104 2133 +29
+ Partials 359 358 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
bcec79e
to
044d976
Compare
/test ci-index-noo-bundle |
pkg/dashboards/dashboard.go
Outdated
var targets []Target | ||
for _, q := range c.Queries { | ||
query := strings.ReplaceAll(q.PromQL, "$METRIC", "netobserv_"+c.mptr.Spec.MetricName) | ||
query = fmt.Sprintf("topk(7, %s)", query) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why top 7 here ? Can't it be configurable to fine grain Prom perfs ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
100% subjective yes, but from personal testing it was the best compromise to see relevant info without overloading the charts. Top 10 easily leads to overcrowded charts (especially as it's a top per datapoint, not a "global" top); while too small top leads to showing more partial metrics/chunks. Of course that's very dependent on what we run on the cluster.
So yes I agree it can be made configurable.
We just need to care about finding a good balance between too much and too few settings.
I guess it doesn't hurt to add that one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool ! thanks @jotak
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done in 5b02dd1
New images:
They will expire after two weeks. To deploy this build: # Direct deployment, from operator repo
IMAGE=quay.io/netobserv/network-observability-operator:e1458c2 make deploy
# Or using operator-sdk
operator-sdk run bundle quay.io/netobserv/network-observability-operator-bundle:v0.0.0-e1458c2 Or as a Catalog Source: apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: netobserv-dev
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/netobserv/network-observability-operator-catalog:v0.0.0-e1458c2
displayName: NetObserv development catalog
publisher: Me
updateStrategy:
registryPoll:
interval: 1m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks @jotak !
Do we need to provide more examples ? 🤔
I'm thinking about optionnal features (Drops / DNS / RTT). That can be done in followups
There's already drops/dns/rtt metrics with their charts as part of the predefined metrics, which can be enabled via the includeList; but we could have more "combined" examples such as external traffic latency; I can add that |
- Add dashboard config to metrics API - Use this API internally for predefined dashboards - Allow using SingleStats - New dedicated buckets for latency histograms
- Allow users to reference/create new dashboards (this requires the monitoring controller to fetch all dashboards from the dashboards namespace) All dashboard names are prefixed "NetObserv / " ; so, rename the main dashboard as "NetObserv / Main" - Add/update tests
an Overview section
5938f74
to
ebf5897
Compare
- generate markdown API reference - document in Metrics.md
/ok-to-test |
New images:
They will expire after two weeks. To deploy this build: # Direct deployment, from operator repo
IMAGE=quay.io/netobserv/network-observability-operator:8487560 make deploy
# Or using operator-sdk
operator-sdk run bundle quay.io/netobserv/network-observability-operator-bundle:v0.0.0-8487560 Or as a Catalog Source: apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: netobserv-dev
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/netobserv/network-observability-operator-catalog:v0.0.0-8487560
displayName: NetObserv development catalog
publisher: Me
updateStrategy:
registryPoll:
interval: 1m |
@jotak - feedback on unit, there's no way to leave it empty as instruction suggest, perhaps it's possible in yaml, is it possible to set custom units like fps (flows per second) ? |
Co-authored-by: Mehul Modi <memodi@redhat.com>
No we can't set custom units (that wouldn't work with the console's dashboard engine), but you're right we need to add something as a fallback unit .. perhaps "numeric" |
/ok-to-test |
New images:
They will expire after two weeks. To deploy this build: # Direct deployment, from operator repo
IMAGE=quay.io/netobserv/network-observability-operator:e973630 make deploy
# Or using operator-sdk
operator-sdk run bundle quay.io/netobserv/network-observability-operator-bundle:v0.0.0-e973630 Or as a Catalog Source: apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: netobserv-dev
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/netobserv/network-observability-operator-catalog:v0.0.0-e973630
displayName: NetObserv development catalog
publisher: Me
updateStrategy:
registryPoll:
interval: 1m |
@jotak: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/label qe-approved |
@jotak: This pull request references NETOBSERV-1343 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.