Broker Notification Configuration

As of build 2026-07-25, you can control what broker-events generate operator notifications, and which are only logged to the event log. It is a new system configuration page. This means the configuration will be part of the installation procedure of the Neuron as well. Each configuration have an associated environment parameter.

You find the new configuration page from the administration page, under Notarius Electronicus and Notifications.

Pressing the button (or opening the page via the drop-down menu), opens a page where individual event notifications can be enabled or disabled. For nodes with a lot of events, it might be more efficient and less distracting to disable certain notifications, and process them in bulk regularly instead of managing them individually.

Environment Variables

The following table lists environment variables that can be used to control the configuration of notifications:

Environment Variable	Description
BROKER_NOT_ACCOUNT_CREATED	If a notification should be sent when a new account is created.
BROKER_NOT_ACCOUNT_DELETED	If a notification should be sent when a new account is deleted.
BROKER_NOT_LEGAL_ID_RECEIVED	If a notification should be sent when a new a Legal ID application is received.
BROKER_NOT_OTHER_LEGAL_IDS	If a notification should be sent for every existing valid Legal ID that exists when a new Legal ID application is received.
BROKER_NOT_PEER_REVIEW_APPROVED	If a notification should be sent when a peer review of a Legal ID has been approved.
BROKER_NOT_LEGAL_ID_AUTO_APPROVED	If a notification should be sent when a Legal ID application has been automatically approved.
BROKER_NOT_LEGAL_ID_AUTO_REJECTED	If a notification should be sent when a Legal ID application has been automatically rejected.
BROKER_NOT_CONTRACT_PROPOSAL_RECEIVED	If a notification should be sent when a contract proposal has been received.
BROKER_NOT_ACCOUNT_RECOVERY_REQUEST	If a notification should be sent when an account recovery request has been received.
BROKER_NOT_API_KEY_CREATED	If a notification should be sent when an API key has been created.
BROKER_NOT_FEEDBACK_RECEIVED	If a notification should be sent when feedback has been received.
BROKER_NOT_ACCOUNT_REQUESTED	If a notification should be sent when an account has been requested.
BROKER_NOT_API_KEY_REQUESTED	If a notification should be sent when an API key has been requested.

#neuron, #admin

Performance Reports

A new set of reports are available to operators of a Neuron® (since build 2025-02-12). The performance of the neuron, such as CPU, free internal memory and free hard disk space is sampled. Statistics, such as Mean, Min, Max, Variance and Standard Deviation is calculated in windows of one minute and then stored. The new performance reports allows operators to view historically how these parameters change.

The performance reports are available in a new data source called Reports. (Apart from the performance reports, the new data source also houses previous reports available in the Protocols and Data data sources, which have now been removed.) You can access the Reports data source via any harmonized interface used to administer the Neuron®, or using the Node Explorer (available from the administration page, under Sources & Nodes.

By executing the CPU Usage report, you can see if there’s sufficient CPU power, or if the service is under pressure during certain times, for instance:

The Free Memory report lets you know if the computer hosting the Neuron® has sufficient internal memory (RAM) for the processes that runs on it:

The Free HD report shows available Hard Disk space on the drive that hosts the application data folder for the Neuron®.

Performance Monitoring

While sampling the performance parameters, monitors also check if the values indicate resources are running out. If CPU usage is elevated, or free internal memory or hard disk space is low, alerts are generated to notify operators about the situation. If conditions worsen, emergencies are logged to alert the operators, before the machine stops working.

#new, #neuron, #features, #admin

Configuring HTTP/2 settings on a Neuron

From build 2025-01-24 it is possible to configure HTTP/2 settings in the Nueron®. These are settings that are available in the gateway.config file. They are applied during startup of the Neuron®, and require a restart of the Neuron®, if changed.

You can also edit the settings from the Sources & Nodes option in the administrative menu. In the screen that appears, you select the Gateway configuration source, and the WebServer node:

Pressing the Edit... button shows the properties of the WebServer node. Scrolling down, you find the HTTP/2 header, and the corresponding HTTP/2-related attributes you can configure. After setting the values, press the Apply button. This will update the gateway.config file. You have to restart the Neuron® for the changes to take effect.

For a reference to the meaning of these settings, see the following normative texts:

• RFC 7540 - Hypertext Transfer Protocol Version 2 (HTTP/2)
• RFC 9218 - Extensible Prioritization Scheme for HTTP

#new, #features, #neuron, #admin, #operations

Quick-Admin-Login

It is now possible to associate a legal ID (or a Neuro-Access ID) with an administrative account on the Neuron®, from the build 2025-01-21. The login page now shows an animated QR code that you can can using the Neuro-Access app.

To associate a Neuro-Access ID (or legal ID) to a user account, edit the corresponding user. You will see three fields that have to be provided: The current Legal ID and the corresponding personal number and country code. You can get these from quicklog.in if not known.

Once the information has been provided, you can login to the administrative console of the Neuron® using the corresponding legal ID.

Updating ID

As legal identities are limited in time, there will come a point when an ID needs to be updated. This will obsolete the old ID, which will be replaced by a new one. As long as this process is followed (i.e. old ID is obsoleted) and the new ID contains the same personal number and country code you can also use the new ID to login to the same user account. The legal identity reference will be correspondingly updated, and an event will be logged, for reference.

Event Log

All administrative logins are logged to the event log, so too the logins using Neuro-Access digital identities. The message text and corresponding properties may be different. Any problems such as duplicate legal identities associeted with multiple accounts, etc., will also be displayed in the event log.

#new, #features, #neuron, #admin, #neuro-access, #quicklogin

Viewing HTTP Statistics

Each Neuron® collects statistics of how the HTTP interface on the Neuron® is used. You can view this statistics from the Node Explorer available from the Administration page, or from any harmonized interface you can access with sufficient privileges.

In the Node Explorer, Open the source Protocols and select the HTTP node. From the details view, press the Commands button. The Statistics command will be shown. Press this button to open the query parameters. You can either show statistics from the entire logged period, or you can enter a time interval over which the statistics will be shown:

Click the Execute button to execute the query. A report will be generated. The report will contains the number of requests per day, over the time period:

You can also see the amount of data transmitted and received, per day:

You can see calls distributed by HTTP method (including invalid method used by strange actors):

Next graph shows calls made by different user agents, as defined by the User-Agent HTTP header. To collect user agents, digits and contents within parenthesis have been replaced by # and ... respectively.

Then follows calls per source, as defined by the From HTTP header. The @ character can signify either an e-mail address, or an XMPP-address (in case HTTPX is used). All IP address sources are collected into one record.

Finally, a graph of which registered resources receive the calls. This graph only counts registered resources, and not the sub-resources each resource might handle. The folder name for a File folder resource will therefore be counted each time a file in that folder is requested.

#new, #features, #admin, #neuron