observability #1449
Closed
observability #1449
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
ctauchen
reviewed
May 9, 2024
use-cases/observability.mdx
Outdated
|
|
||
| Specific examples of how to use these observability features for these issues can be found below. | ||
|
|
||
| ### Most-detailed observability |
There was a problem hiding this comment.
This title reads a bit awkward. I think you should ditch the word 'observability' as you did with the previous titles.
Perhaps something along these lines?
- Fine-grained log analysis
- Visualizing logs
- Observing detailed log output
use-cases/observability.mdx
Outdated
| * *Kibana* - The Kibana dashboards have a "unique-domains" widget that lists the top values of dest_domains from flow logs, with a record count. | ||
| Clicking on a domain name in that widget will filter all flows that sent traffic to that FQDN. | ||
|
|
||
| To see this in Kibana, watch [this video](https://fast.wistia.com/embed/channel/lhjf79y3oy?wchannelid=lhjf79y3oy&wmediaid=huq9luzvux) |
use-cases/observability.mdx
Outdated
| * *Kibana* - Dashboards and logs in Kibana can be queried using kql to search for flows with specific process ids, names or arguments. | ||
| This will return all flows that match, helping to identify the source and destination of flows for those processes. | ||
|
|
||
| To view an example using Kibana to filter and identify flows related to log4j communication, watch [this video](https://fast.wistia.com/embed/channel/lhjf79y3oy?wchannelid=lhjf79y3oy&wmediaid=ooka4wvfxz) |
use-cases/observability.mdx
Outdated
Comment on lines
306
to
308
| ##### Identify flows with “bytes_in : 0” | ||
|
|
||
| Flows with “bytes_in : 0” and “action : allow” indicate that an upstream firewall denied a flow, or the server is not responding to the connection. |
There was a problem hiding this comment.
For code snippets, please format with backticks:
`bytes_in : 0`
use-cases/observability.mdx
Outdated
|
|
||
| ### What is observability? | ||
|
|
||
| Observability is the ability to understand the internals of a system by analyzing the internals of a system. |
There was a problem hiding this comment.
Suggested change
| Observability is the ability to understand the internals of a system by analyzing the internals of a system. | |
| People use observability tools to understand a complex system by visually analyzing what's going on in that system. |
A suggestion.
use-cases/observability.mdx
Outdated
| In complex systems, with lots of dynamic, interconnected parts, observability puts a visual frontend on what would otherwise likely be a series of recursive commands in a CLI to obtain the same information. | ||
| What that front-end is will depend on the software that’s integrated within the cluster, and will likely depend on which internals are being shown, and who the target audience is. | ||
| One example might be a dashboard, showing various metrics to an end-user who needs an overview of a system to monitor it’s health. | ||
| Observability could also go more granular than that, representing visually how different resources installed in the cluster are connected and dependent on each other. |
There was a problem hiding this comment.
Suggested change
| Observability could also go more granular than that, representing visually how different resources installed in the cluster are connected and dependent on each other. | |
| At a more granular level, observability tools can help you visualize how different resources installed in the cluster are connected and dependent on each other. |
A suggestion
use-cases/observability.mdx
Outdated
| What that front-end is will depend on the software that’s integrated within the cluster, and will likely depend on which internals are being shown, and who the target audience is. | ||
| One example might be a dashboard, showing various metrics to an end-user who needs an overview of a system to monitor it’s health. | ||
| Observability could also go more granular than that, representing visually how different resources installed in the cluster are connected and dependent on each other. | ||
| In summary, observability is a way to visualize, organize and understand what’s going on in our Kubernetes clusters. |
5 tasks
|
Changes picked up in #1470 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: