Skip to content

[Update] Remove mentions of no-longer maintained or recommended observability tools and stacks. #273

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[Update] Remove mentions of no-longer maintained or recommended observability tools and stacks. #273

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c363793
Update observability.rst
simskij May 26, 2025
b9557f4
Update observability.rst
simskij May 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 4 additions & 19 deletions how-to/observability.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,8 @@ Observability

In Ubuntu, it is recommended to use the
`Canonical Observability Stack <https://documentation.ubuntu.com/observability/>`_
to monitor your infrastructure.
to monitor your infrastructure. For more information, see the following links:

However, you can also use the classic Logging, Monitoring and Alerting (LMA)
stack.

.. toctree::
:titlesonly:

Set up your LMA stack <observability/set-up-your-lma-stack>
Comment on lines -13 to -16
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm happy for us to take away the LMA stack, since this has been fully superseded by COS. However, I would ask you to also delete the lma stack page in question, otherwise the documentation will fail to build because of the page existing without being in a toctree.


If you do not need a full LMA stack, there are some other supported tools that
can provide similar capabilities.

.. toctree::
:titlesonly:

Install Logwatch <observability/install-logwatch>
Install Munin <observability/install-munin>
Install Nagios Core 3 <observability/install-nagios>
Use Nagios with Munin <observability/use-nagios-with-munin>
Comment on lines -18 to -27
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you please reinstate this content? These options need to still exist, even if COS the way we officially recommend people to handle observability. Towards 26.04 we can look at replacing this with more up-to-date options but for now I'd like us to keep it, for the benefit of users who can't (or don't want to) use COS.

- `Getting started with COS Lite <https://documentation.ubuntu.com/observability/tutorial/installation/getting-started-with-cos-lite/>`_
- `How to integrate COS Lite with uncharmed applications <https://documentation.ubuntu.com/observability/how-to/integrating-cos-lite-with-uncharmed-applications/>`_
- `The OpenTelemetry Collector snap <https://snapcraft.io/opentelemetry-collector>`_
Copy link
Collaborator

Choose a reason for hiding this comment

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

These links are a really helpful addition, but if we want to tempt people to use COS we should provide a bit more context around these links.

I think if we can use this space to disambiguate the difference between the COS and COS lite use cases, and say what OTC does and what use case it is for, it will help our readers to understand which of the options they should use for their situation, which will in turn help increase the adoption.