What is the Dashboard?

The Nodinite Dashboard empowers you to visualize, share, and act on business-critical statistics and KPIs—all in one place. As the first page end-users see in the Nodinite Web Client, the Dashboard is designed to maximize engagement and deliver actionable insights.

With the Nodinite Dashboard, you can:

✅ Share real-time statistics and KPIs with your business and stakeholders
✅ Integrate data from both Nodinite and external REST-based APIs
✅ Customize the layout and content to fit your unique business needs
✅ Encourage frequent visits with dynamic, relevant content

Nodinite provides options to help you maximize the end-user experience:

• Sharing is caring – Provide valuable content for end-users based on all available data, not only from within Nodinite but also from external REST-based APIs and Reports.
• Configurable content – Data in the widgets is individually refreshed based on user-defined thresholds to provide near real-time data.
• Customizable layout – Design the layout of the Dashboard as you like, to fit your business.

Out of the box	Customized example

Here's an example of the 'out of the box' and a customized Dashboard.

Tip

Be sure to add content to the Dashboard that encourages your end-users to visit it frequently!

How Dashboard Data Flows

The diagram below shows how data flows into the Dashboard from various sources, empowering business users with real-time insights:

Dashboard data flows from internal Nodinite systems and external APIs through configurable widgets to deliver insights to business users.

What data can I put on the Dashboard?

The Dashboard supports a wide range of data sources, allowing you to present statistics and KPIs from Nodinite and beyond. You can visualize metrics in multiple formats:

• Pie charts
• Tables
• Metrics chart: Bar charts
• Line charts
• Lists
• Text and numbers

The Dashboard features both mandatory built-in Dashboard items and optional custom Dashboard items.

Built-in Dashboard items

1. Information from Monitor Views available for the currently logged-on User
2. Offline internal core services
   • Logging Service
   • Monitor Views
3. License issues
4. Log Events per day (numeric data from Log Views), with warning and error levels set by LogEventsPerDayThresholds.^{New 7.12}
5. Statistics for Integrations in the Repository Model.
6. Statistics for Endpoints in the Repository Model.
7. Statistics for Message Types in the Repository Model.
8. Statistics for Services in the Repository Model.
9. Statistics for Contracts in the Repository Model.
10. Alarm Queue Alert notification (if any) requiring administrative attention.^{New 7.x}

Administrators can also pin User Notifications, such as a planned maintenance window, to the top of the Dashboard.

1. Monitor Views

A pie chart displays the current state of available Monitor Views. Click any part of the pie chart to open the list of matching Monitor Views.

Pie chart showing the state of Monitor Views. Click to drill down for details.

Click the Customize button to open a modal with the option to view the current state of resources from selected Monitor View.

Modal for customizing which Monitor Views are displayed.

2. Offline internal core services

If any of the built-in internal core services, such as the Monitoring Service or the Logging Service, are offline, unavailable, or stopped, all users are notified at the top of the dashboard that there is a problem that needs to be addressed by an Administrator.

Notification for offline internal core services.

3. License issues

If there is a problem with the license key (most often expiration date is nearing) information about this is available on top in the dashboard. This is a problem that needs to be addressed by an Administrator.

4. Log Events per day

The number of archived transactions per day (filter may be applied to compare the last 4 weeks).

Bar chart showing Log Events per day.

^{New 7.12} The chart warns when a day exceeds the levels set in the LogEventsPerDayThresholds System Parameter: above the warning level the bars and banner use the warning colour, above the error level the error colour. All users see the warning; only members of the built-in Administrator Role see the Clear and Edit System Parameter buttons. If you are not an Administrator, contact one to investigate and clear the warning.

The banner and the dashed warning and error levels on the Log Events per day chart. This test environment uses levels of 300 and 500; set LogEventsPerDayThresholds from your own normal volume.

Warning

A day above the levels is often a sign that logging has gone rogue, for example debug logging left on in production. In one support case, integrations logged about 150 million Log Events per day and Nodinite was blamed for the resulting performance problem. Find and fix the source before you clear the warning; see Investigate a Breach.

5. Statistics for Integrations

Statistics about the creation of Integrations from within the Repository Model.

Statistics for Integrations in the Repository Model.

6. Statistics for Endpoints

Statistics about the creation of Endpoints from within the Repository Model.

Statistics for Endpoints in the Repository Model.

7. Statistics for Message Types

Statistics about the creation of Message Types from within the Repository Model.

Statistics for Message Types in the Repository Model.

8. Statistics for Services

Statistics about the creation of Services from within the Repository Model.

Statistics for Services in the Repository Model.

9. Statistics for Contracts

Statistics about the creation of Contracts from within the Repository Model.

Statistics for Contracts in the Repository Model.

10. Alarm Queue Alert

^{New 7.x} While the Alarm Queue holds any entry, every user sees the critical status 1 Critical errors detected – Nodinite is unable to send one or more alerts. Users may not be notified when Monitor Views are in an unexpected state. Contact the System Administrator. at the top of the Dashboard and every other page. View opens the Alarm Queue, which only users with the Administrator Role can manage. The number counts status messages, not queued alerts, so it says 1 however many alerts are waiting.

Example: Nodinite Alarm Queue alert in the Nodinite Web Client, indicating pending entries requiring administrative attention.

Custom Dashboard Items

Extend the Dashboard with custom content beyond built-in widgets:

1. HTML Widgets - Static environment badges and team announcements
2. Metrics Charts - Performance graphs from Monitoring Agents

For Power BI reports on Nodinite data, use the Web API in Power BI itself: a widget can't embed Power BI.

Learn more: Custom Dashboard Items - Complete guide to extending the Dashboard

Warning

HTML widgets are a transitional feature: Nodinite 8 replaces them with a more secure extensibility solution. Widgets run in a sandboxed iframe with a Content Security Policy that blocks inline scripts and content from other sites.

Available Metrics Sources

• Windows Server Monitoring Agent - CPU, Memory, Disk, Network, IIS Performance Counters
• BizTalk Server Monitoring Agent - Throttling, Spool tables, TrackingData
• Web Service Monitoring Agent - Response-time monitoring
• Dynamics 365 Monitoring Agent - Logon statistics and history

See step-by-step guide: Custom Dashboard Items includes complete instructions for adding metrics charts and custom HTML content.

Next Steps

Monitor Views - Explore Monitor View features
Custom Dashboard Items - Extend the Dashboard with custom content

Related Topics

Administration
Alarm Queue
Endpoints
Logging Service
LogEventsPerDayThresholds - Warning and error levels for the Log Events per day chart
Monitoring Agents
Monitoring Service
Repository Model
Users
User Notifications
Web API
Web Client