add Observability and Analysis category

[MarckK]

Pre-submission checklist:

Please check each of these after submitting your pull request:

• Are you only including a repo_url if your project is 100% open source? If so, pick the single best GitHub repository for your project, not a GitHub organization.
• Does it follow the guidelines for new entries?
• Have you added an SVG to hosted_logos and referenced it there?
• Does your logo clearly state the name of the project/product and follow logo guidelines?
• Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
• ~5 minutes after opening the pull request, the CNCF-Bot will post a link for you to preview your changes. Have you confirmed that they are correct and then added a comment to the PR saying "LGTM"?

[netlify]

✔️ Deploy Preview for cdf-landscape ready!

🔨 Explore the source changes: 80139e7

🔍 Inspect the deploy log: https://app.netlify.com/sites/cdf-landscape/deploys/61e53f07e65002000715d953

😎 Browse the preview: https://deploy-preview-203--cdf-landscape.netlify.app

[MarckK]

This is an entirely trial PR, to map out landscape category changes discussed at landscape wg meeting and #195.

There remains too much overlap on the landscape with the categories proposed in PR, especially around
monitoring:

Additional Note: So as to avoid having to restructure the layout of landscape, I replaced the current Change Management category with Observability and Analysis. This is a temporary hack to be able to easily play around with new category. There is no intention to remove Change Management category from the CDF landscape at this time.

[MarckK]

Hi @tdcox @sbtaylor15 @TracyRagan @tracymiranda @oleg-nenashev,
I'm looking for further feedback and input in this section (see comments and screenshot above).

Open to suggestions to refine naming and categorisation in this area!

[tdcox]

Architecturally, it would be normal to treat Security and Observability as different categories, but include Monitoring within Observability.

[MarckK]

Thank you, @tdcox!
Sometimes I do need to be given implied permission, or encouragement, to go change someone else's prior work 😅

Currently, the prototype (as can be viewed in preview) looks like:

We'll not discuss DevSecOps/Security in this PR, although that does need to be addressed separately.

For changes to the categories shown in the above screen shot, I'd likely put Monitoring & Logging in one category.
What other changes would you suggest?

[tdcox]

That looks better. At this point we start to get into nuanced conversations about monitoring being an active process and logging being a passive one…

Pragmatically, you will need to set a granularity for the document and make the decision to lump stuff together at that granularity. In reality, it’s fractal all the way down and you can continue to sub-categorise everything, the closer you get to it.

[MarckK]

Building in the feedback we've had so far, the section now looks like:

This is still a prototype for the section and any and all feedback is welcome!

[e-backmark-ericsson]

CD Events should go into the Tracing and Messaging sub category in accordance with this proposal, once the needed data for CD Events is set up (#192)

[oleg-nenashev]

The CDF Events SIG meeting supports this proposal (Dec 06, 2021)