Skip to content
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

Make eventing components observable #1722

Merged
merged 8 commits into from
Aug 27, 2019

Conversation

sayanh
Copy link
Contributor

@sayanh sayanh commented Aug 22, 2019

Fix the following components and make them scrapable:

  • eventing-controller
  • broker ingress
  • filter
  • sources-controller
  • Remove hard coded annotation which was used for Prometheus

For the following sources, I'll create a separate PR:

  • cronjobsource
  • containersource
  • apiserversource

See #1693

Related PR in Serving.

Proposed Changes

  • Make eventing controller scrappable
  • Add dashboard for reconciler

Release Note

NONE

- Enable scrapping of eventing-controller
- Add eventing reconciler dasshboard
@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 22, 2019
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 22, 2019
@knative-prow-robot knative-prow-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 22, 2019
@knative-prow-robot knative-prow-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 22, 2019
@knative-prow-robot
Copy link
Contributor

Hi @sayanh. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@knative-prow-robot knative-prow-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 22, 2019
@@ -17,6 +17,608 @@
# --patch "$(cat 100-grafana-dash-eventing.yaml)" -n knative-monitoring
---
data:
knative-eventing-reconciler-dashboard.json: |+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The eventing controllers will show up in the Knative Serving Controller dashboards from my testing.

Copy link
Contributor Author

@sayanh sayanh Aug 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True that. I removed this dashboard completely. We'll use Knative Serving - Reconciler dashboard but I've changed the name to Knative - ReconcilerPR. And of course, we'll take all of the monitoring components out of serving as in here. By the way, where can I find Knative Serving Controller dashboard? I just see the following dashboards.
Screen Shot 2019-08-23 at 15 18 24

rm tmp.prometheus-scrape-kn-eventing.yaml
rm tmp.prometheus-scrape-config.yaml
```

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you are going to add a new scrap job eventing-controller to Prometheus scrap configuration. But the instructions look very complicated. Do you want to try "kubectl patch configmap prometheus-scrape-config ..." ?

An example is that how we add the eventing dashboard to the configmap grafana-dashboard-definition-knative :
kubectl patch configmap grafana-dashboard-definition-knative --patch "$(cat config/monitoring/metrics/grafana/100-grafana-dash-eventing.yaml)" -n knative-monitoring

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@daisy-ycguo The problem here is the scrapping config needs to be a part of the same file(key) in the configmap and we can't patch like the example you posted. Hence this complicated way of doing things.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sayanh Thank you for clarify. I understand now, but still feel complicated. I wonder if kubectl patch configmap --type json ... could help. Here is a reference to json patch

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is just a workaround until we get the prometheus operator in. So I'm fine with it.

@knative-prow-robot knative-prow-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 23, 2019
@sayanh sayanh changed the title Make eventing controller observable Make eventing components observable Aug 23, 2019
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 26, 2019
@sayanh sayanh marked this pull request as ready for review August 26, 2019 09:03
@knative-prow-robot knative-prow-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 26, 2019
@knative-prow-robot
Copy link
Contributor

@sayanh: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

@n3wscott
Copy link
Contributor

/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 26, 2019
@@ -283,7 +283,7 @@ func TestReconcileCRD(t *testing.T) {
WantCreates: []runtime.Object{
NewService(filterServiceName, testNS,
WithServiceOwnerReferences(ownerReferences()),
WithServiceAnnotations(resources.FilterAnnotations()),
WithServiceAnnotations(map[string]string{}),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this call to WithServiceAnnotations can be removed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -459,7 +459,7 @@ func TestReconcileCRD(t *testing.T) {
WantCreates: []runtime.Object{
NewService(ingressServiceName, testNS,
WithServiceOwnerReferences(ownerReferences()),
WithServiceAnnotations(resources.IngressAnnotations()),
WithServiceAnnotations(map[string]string{}),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@nachocano
Copy link
Contributor

@capri-xiyue this will fix the infra issue you were having.

@nachocano
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2019
@nachocano
Copy link
Contributor

@n3wscott for approval

@n3wscott
Copy link
Contributor

/approve

Thanks!

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: n3wscott, sayanh

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2019
@knative-prow-robot knative-prow-robot merged commit 359776f into knative:master Aug 27, 2019
@sayanh sayanh deleted the set-up-prometheus-infra branch August 27, 2019 15:24
aslom pushed a commit to aslom/eventing that referenced this pull request Sep 5, 2019
* Make eventing controller observable
- Enable scrapping of eventing-controller
- Add eventing reconciler dasshboard

* Retain vendor license

* Removed eventing reconciler dashboard

* Make broker filter and ingress scrapeable

* Removed hard coded annotation for prometheus
- Refer prometheus-operator/kube-prometheus#16

* Made sources-controller observable

* Remove sources metrics service

* Fixed as per PR comments
matzew added a commit to matzew/eventing that referenced this pull request May 3, 2022
…t-proxy-some-headers

Do not proxy some headers from reply
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants