-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add Crossplane Metrics Documentation #802
Add Crossplane Metrics Documentation #802
Conversation
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
35f9e7e
to
9a60cd0
Compare
@jbw976, could you please take a look? |
Signed-off-by: shwethamuralikrishnaa [email protected] Signed-off-by: shwethamuralikrishnaa <[email protected]> Signed-off-by: Pierluigi Lenoci <[email protected]>
Signed-off-by: Pierluigi Lenoci <[email protected]>
5b306f6
to
47da6d6
Compare
@AdamRussak, those headers are the same across all pages.
|
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.
@Shwethamuralikrishnaa @pierluigilenoci Thanks for this valuable contribution. Could we please add (duplicate) the metrics page under the /content/v1.17
path as well please.
@jbw976 I'm wondering if "Concepts" is the best area for this content? Feels like a mixture of guides/API reference as well 🤔. That said I don't strong about this, its better to have this info in the docs than bikeshedding about where it should be.
39511ee
to
d501140
Compare
@pierluigilenoci please have a look at signing off your commits so it can pass the DCO check |
Signed-off-by: Pierluigi Lenoci <[email protected]>
d501140
to
4a0af10
Compare
@jeanduplessis all commit signed, duplicated the content in v1.17 |
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.
I'm happy with these as a good start that can be iterated on going forward. I'll wait for @jbw976 to confirm he's happy with the location of the content.
@pierluigilenoci removing of the table header has caused the build to fail |
Why?
|
Signed-off-by: Pierluigi Lenoci <[email protected]>
4e84185
to
0b7ce7d
Compare
@AdamRussak solved. Could you please approve it again? |
Signed-off-by: Pierluigi Lenoci <[email protected]>
content/master/concepts/metrics.md
Outdated
| {{<hover label="crossplane_managed_resource_first_time_to_readiness_seconds_bucket" line="27">}}crossplane_managed_resource_first_time_to_readiness_seconds_bucket{{</hover>}} | The time it took for a managed resource to become ready first time after creation | | | ||
| {{<hover label="crossplane_managed_resource_first_time_to_reconcile_seconds_bucket" line="28">}}crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{{</hover>}} | The time it took to detect a managed resource by the controller | | | ||
| {{<hover label="upjet_resource_ttr_bucket" line="29">}}upjet_resource_ttr_bucket{{</hover>}} | Measures in seconds the `time-to-readiness` `(TTR)` for managed resources | | | ||
{{< /table >}} |
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.
Can you please close this?
content/v1.17/concepts/metrics.md
Outdated
| {{<hover label="crossplane_managed_resource_first_time_to_readiness_seconds_bucket" line="27">}}crossplane_managed_resource_first_time_to_readiness_seconds_bucket{{</hover>}} | The time it took for a managed resource to become ready first time after creation | | | ||
| {{<hover label="crossplane_managed_resource_first_time_to_reconcile_seconds_bucket" line="28">}}crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{{</hover>}} | The time it took to detect a managed resource by the controller | | | ||
| {{<hover label="upjet_resource_ttr_bucket" line="29">}}upjet_resource_ttr_bucket{{</hover>}} | Measures in seconds the `time-to-readiness` `(TTR)` for managed resources | | | ||
{{< /table >}} |
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.
Can you please close this?
@jbw976, please give us feedback. |
FWIW that was my first thought too. I don't think this is a Crossplane concept. Not sure where the best fit for it is though. |
content/master/concepts/metrics.md
Outdated
This page offers explanations of various metrics gathered from Crossplane, which are essential for effective monitoring and alerting in your Crossplane environment. | ||
Understanding these metrics help you maintain the health and performance of your resources, ensuring to identify and address any issues. | ||
Please note that this document focuses on Crossplane specific metrics and doesn't cover standard Go metrics. |
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.
It'd be useful to mention:
- That these are prometheus style metrics
- Where they're exposed (i.e. the port and URL)
- How to enable them (iirc they're not on by default)
I don't think it's worth explaining what Prometheus style metrics are or how they work, but we should link to the Prometheus documentation for those who are unfamiliar.
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.
Really cool to see you take the initiative to document this useful information
@Shwethamuralikrishnaa and @pierluigilenoci. Thank you for taking the time to do so!
I know Vale is a bit of a pain, but hopefully that pain is reduced some with all the fixes we have cooking in #810. I will hold off on merging that one though so you don't have to deal with any merge conflicts 😇
content/master/concepts/metrics.md
Outdated
Please note that this document focuses on Crossplane specific metrics and doesn't cover standard Go metrics. | ||
|
||
|
||
| Metric Name | Description | Further Explanation | |
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.
on the preview site, the table is a bit hard to read/parse because there are no visible rows: https://deploy-preview-802--crossplane.netlify.app/v1.17/concepts/metrics/
Take a look at the table for Customize the Crossplane Helm chart
on
https://github.com/crossplane/docs/blob/master/content/master/software/install.md#customize-the-crossplane-helm-chart
It does some styling directives to make easily visible striped rows - see if that helps with this new table!
For example:
{{< table "table table-hover table-striped table-sm">}}
@negz @jeanduplessis, please tell me where to move it, or just be happy, and we'll move it later. 😜 |
Signed-off-by: Pierluigi Lenoci <[email protected]>
Signed-off-by: Pierluigi Lenoci <[email protected]>
Signed-off-by: Pierluigi Lenoci <[email protected]>
Deployment preview succeeded and the table with the colored rows looks great @pierluigilenoci!! Don't worry about any of the Vale failures, I'll make sure it's still all clean and green in #810 🟢 |
Signed-off-by: Pierluigi Lenoci <[email protected]>
@jbw976, it's too late! 😄 |
@jbw976, what needs to be added to merge with PR if the page looks great and everything else is 🟢 ? |
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.
Thank you very much for continuing to drive this PR and get this important topic documented! 🙇♂️
This PR introduces a new documentation page dedicated to the metrics collected from Crossplane. The page is designed to help users understand the metric and how it can be used to monitor and troubleshoot Crossplane operations