Перейти к содержанию

Blog

24.1.2 release contains 15 bugfixes, optimisations and improvements.

Improvements

MRTitle
{{ mr(8231) }}#2516 Fix column titles and localization for joined datasources in csv-output-reports
{{ mr(8231) }}#2516 Fix column titles and localization for joined datasources in csv-output-reports
{{ mr(8283) }}Add description field to ipprefix ETL.
{{ mr(8350) }}Speedup sync_model_groups query.

Bugfixes

MRTitle
{{ mr(8196) }}Remove unused on_delete_check condition in AuthProfile
{{ mr(8232) }}Fix integrity error when load IPPrefix or IP Address on ETL
{{ mr(8252) }}Change source 'archive' to 'archived' for old AlarmDetail report
{{ mr(8264) }}collections: Gently handle the recoverable deletion errors
{{ mr(8267) }}Check ModelProtectionProfile FK for group deletion
{{ mr(8319) }}#2530 metrics: Refetch service state on CH error

Profile Changes

Juniper.JUNOS

MRTitle
{{ mr(8204) }}Update Juniper.JUNOS

rare

MRTitle
{{ mr(8297) }}HP.Aruba. Fix page mode works
{{ mr(8323) }}HP.Aruba. Fix page mode.

Collections Changes

MRTitle
{{ mr(8351) }}#2536 Add Restore transition to Managed Object Default workflow.

Deploy Changes

MRTitle
{{ mr(8437) }}Fix checks conditions

24.1 release contains 554 bugfixes, optimisations and improvements.

CSR Proxying for Obtaining a Valid SSL Certificate for Software Evaluation

The proposed scheme, developed by Dmitry Volodin of Gufo Labs, is designed for software publishers distributing software for EVALUATION PURPOSES and requiring a valid SSL certificate to allow users access to the web interface.

The proposed scheme offers a streamlined process for users by redirecting their browsers to a well-known entry point like https://go.example.com:<port>/ immediately after installation. It eliminates the need for additional user steps and ensures the private key remains secure and is not shared with any external parties.

Introducing Our Revamped Telegram Group: Now in English and Russian!

At NOC, we are excited to announce a significant update to our official Telegram group! Our dedicated team has been hard at work, revamping the group to provide you with an even better experience. We are proud to present a brand new thematic group, now available in both English and Russian languages.

Why the Revamp?

As part of our commitment to our community, we wanted to create a more inclusive and engaging space for NOC enthusiasts around the world. While our original group served as a hub for networking and discussions, we saw an opportunity to make it even better.

Hosting a Mkdocs-generated Site Using Nginx

Creating exceptional software documentation is a pivotal ingredient for product success. The NOC Team has been on a relentless journey with Project Aegeus to make our documentation truly shine. While top-notch content is essential, the delivery process plays a crucial role in shaping the user experience. In this post, we're shifting our focus to delivery, where we'll reveal some tricks that can take your documentation from good to great.

Mkdocs, especially when adorned with the stylish mkdocs-material theme, is an outstanding tool for crafting project documentation. The outcome is a directory brimming with polished HTML files and static assets. Unlike popular CMS platforms like Joomla or WordPress, your output is a self-contained directory that doesn't rely on additional runtime services or databases. This independence makes it incredibly easy to serve your documentation directly to your audience. While services like "GitHub Pages" and "Read the Docs" have their allure, there's a compelling case for hosting your documentation independently. We, for instance, rely on the rock-solid Nginx web server. In the following sections, we'll offer you a glimpse into our setup and share some simple yet highly effective tweaks to enhance performance.

Проект "Авгий": Объединение документации NOC

В NOC в настоящее время проводится реформирование нашей документации в рамках "Проекта Авгий", с целью предоставить нашим пользователям более консистентную и актуальную документацию.

Проблема

Ранее наша документация была разделена на английские и русские разделы, которые не соответствовали друг другу и имели чрезмерно сложные структуры. Кроме того, большая часть документации все еще размещалась в старой системе Confluence. В результате было сложно для пользователей получить необходимую информацию, а для разработчиков - поддерживать документацию в актуальном состоянии.