Logo
Resources
Documentation Portal Ideas Portal Guardsix Academy License Portal
Resources
Documentation Portal Ideas Portal Guardsix Academy License Portal Use Case Navigator
Sign in
  1. Guardsix Servicedesk
  2. Knowledge Center
  3. Announcements

End of life: Logpoint Agent (Standalone and Centralized)

Avatar Dinesh Aryal
September 29, 2026 09:22
Follow
End of life: Logpoint Agent (Standalone and Centralized) | Guardsix

The Logpoint Agent, in both its Standalone and Centralized forms, is reaching end of life. It is being replaced by the Guardsix Log Collection Agent, our own first-party agent for log collection. This notice sets out the dates that matter, what changes for you, and where to go to migrate.

November 2027End of support

From November 2027 the Logpoint Agent (Standalone and Centralized) receives no further updates or fixes and falls outside support. We recommend completing migration to the Guardsix Log Collection Agent by September 2027.

Key dates

  1. 29 September 2026 Announcement date
  2. September 2027 Recommended migration completion
  3. November 2027 End of support for the Logpoint Agent (Standalone and Centralized)

We recommend completing your migration by September 2027. This leaves a clear buffer before support ends and avoids last-minute pressure across your estate.

What is changing

The Logpoint Agent is built on NXLog and uses NXLog-format configuration files. The Guardsix Log Collection Agent is built on an OpenTelemetry foundation and uses a single YAML policy. Core log collection carries across, and the migration guide maps the common settings directly. Some advanced NXLog-specific options are simplified or not yet included.

The Log Collection Agent is built and maintained by us from end to end. It removes the third-party dependency and gives you a simpler, more secure path from your hosts into Guardsix SIEM.

Until November 2027 the Logpoint Agent remains supported and you can keep running it. From that date it will receive no further updates or fixes and will fall outside support.

How to migrate

Migration is documented step by step, and you can run it yourself. Start with our migration guide. It covers what changes, what maps directly to the new configuration, and the few areas that need planning first.

Migration guide Migrate from Logpoint Agent (Standalone)
Open the guide

Work through the guide at your own pace:

  1. Install the Log Collection Agent and keep both agents running side by side.
  2. Confirm your logs are arriving in Guardsix SIEM.
  3. Only then remove the Logpoint Agent.

Log Collection Agent v1.0.1 supports Windows only, and logs are sent over HTTPS rather than UDP syslog, which may need a firewall change. The guide lists the prerequisites in full.

What's coming next

The Log Collection Agent is developing quickly. If you run a more advanced Logpoint Agent deployment, these are the capabilities next in line, in the order we are taking them on, so that every supported setup has a path across well before support ends.

  1. Agent Management Console Q2 2027

    Central management for the Log Collection Agent, so teams running Logpoint Agent Centralized keep a single place to manage their agents at scale.

  2. UDP transport Q3 2027

If one of these is important to your migration, contact your Guardsix account team, who can help you plan your timing around it. If there is another capability you would like to see, you can raise it as an idea in our idea portal.

If you need help

Some setups need planning first: multiple output destinations, UDP transport, failover, or scripting and transformation modules. If any of these apply, or if anything in the guide is unclear, contact your Guardsix account team or open a support ticket. We will help you plan the migration.

Guardsix. Your closest ally in cyber security.

Comments

Article is closed for comments.

Related articles

  • DNS Process Plugin
  • AgentX Server
Was this article helpful? 0 out of 0 found this helpful
Privacy policy    EULA    Terms of service   
Copyright © , Guardsix. All rights reserved.

Note: We use cookies that are essential for the smooth functioning of our website.