Blog on "What's new in Network Observability 1.11"#31
Blog on "What's new in Network Observability 1.11"#31stleerh wants to merge 5 commits intonetobserv:mainfrom
Conversation
|
🚀 PR Preview for netobserv.io has been successfully deployed! |
| - Service deployment model | ||
| - FlowCollectorSlice CRD | ||
| - Zero-click Loki | ||
| - DNS name |
There was a problem hiding this comment.
Maybe add a mention that it's about QName ?
There was a problem hiding this comment.
I added a sentence about this in the "DNS name" section.
| name: websvc | ||
| ``` | ||
|
|
||
| The FlowCollectorSlice instances won't take effect unless they are enabled in the FlowCollector. In OpenShift web console, configure this in the **Processor configuration** in **Slices configuration**. On the terminal, enter `oc edit flowcollector`, and configure the following under the **processor** section: |
There was a problem hiding this comment.
| The FlowCollectorSlice instances won't take effect unless they are enabled in the FlowCollector. In OpenShift web console, configure this in the **Processor configuration** in **Slices configuration**. On the terminal, enter `oc edit flowcollector`, and configure the following under the **processor** section: | |
| The FlowCollectorSlice instances won't take effect unless they are enabled in the FlowCollector. In OpenShift web console, configure this in the **Slices configuration** under **Processor configuration**. On the terminal, enter `oc edit flowcollector`, and configure the following under the **processor** section: |
There was a problem hiding this comment.
I reworded this so it's clearer. I didn't want to say "Slices configuration" first because you don't see this unless you click "Processor configuration" to open this up.
leandroberetta
left a comment
leandroberetta
left a comment
There was a problem hiding this comment.
LGTM with just a minor comment (optional). Thanks @stleerh, very nice blog.
| <br> | ||
| Figure 6. Configure recording rules in the healthRules section. | ||
|
|
||
| Both the recording rules and alerts fall under the umbrella of **healthRules**. When you select a template for a health rule, you will also need to include the corresponding metric. That is done in the **include list** section. Don't worry; a warning will appear if you didn't include the necessary metric. For the DNS-related health rule, you also need to enable the `DNSTracking` feature in eBPF. |
There was a problem hiding this comment.
I think clarifying the inclusion of metrics is good advice, although it’s not always needed. Also, I’m not sure if it’s worth mentioning, but when you include a metric, you overwrite the metrics list, so the user will probably lose other metrics (this is something we’ve discussed improving in the near future).
There was a problem hiding this comment.
Yes, this is what I experienced. I wasn't sure I wanted to mention it here, rather than to file an issue to improve this.
5 participants
No description provided.