- 4 minutes to read

Getting started

Welcome to the Nodinite Getting Started Guide! Unlock the full potential of Nodinite for seamless system integration, proactive monitoring, and self-service logging. Whether you are a technical expert or a business stakeholder, this guide empowers you to:

  • ✅ Achieve true self-service for integration monitoring and logging
  • ✅ Gain instant visibility and control over your business processes
  • ✅ Receive proactive alerts to resolve issues before they impact your business
  • ✅ Access comprehensive documentation and knowledge in one place

The Getting started user guides help end-users of Nodinite, typically using the Web Application called the Web Client. These pages provide clear, actionable information and direct links to in-depth technical documentation as needed.

Nodinite delivers value to all stakeholders by providing up-to-date, relevant information regardless of the integration technology or platform. Explore these core features:

Monitoring Logging Repository
Get alerts whenever there is a problem and fix it before it gets someone else's problem too Find what you are looking for Documented solutions are key to personal independence

Order flow — the self-service journey

Experience how Nodinite enables self-service for a complete order flow. The Order flow journey walks a business user through it, one short task at a time:

# Task You'll be able to Logging Monitoring
1 Find an order by Order Id Search your Log View by Order Id and see every logged step
2 See what happened to an order Read the order as a document, follow its timeline, see the error, add a comment
3 Know when orders stop coming in Read the order-flow state in a Monitor View and get alerts when the count drops

What your administrator sets up once for each task (Log View, Search Field, Stylesheet, Non-Events check, alert recipients) is listed on the journey page. More journeys are listed under Scenarios.

Logging

Find what you are looking for

How to use Logging

Access logged events and payloads using tailored Role based Log Views. Nodinite audits all operations for full traceability.

End-user perspective Administrator perspective
How do I find order '123' that I'm missing? How do I create a Log View where end-users can find orders by Order Id?

What Logging is

Nodinite logs and archives events and data from many system integration platforms. You always find what you need with true end-to-end logging.

Why Logging matters

System integration solutions often span multiple systems, both on-premise and in the cloud. Even identifying the right system to investigate can be a challenge. Nodinite gives you access to all your integration data in one place, eliminating the need for multiple products with steep learning curves and complex pricing.

How Logging works

Nodinite collects events and data using Logging agents or embedded code within integration brokers/applications.

If you are a Developer, start with reading the Asynchronous Logging guide.

Monitoring

Get alerts whenever there is a problem and fix it before it gets someone else's problem too

How to use Monitoring

Manage and access monitored Resources using tailored Role based Monitor Views. Nodinite audits all operations for accountability.

End-user perspective Administrator perspective
How do I know there's a problem with my Order integration? How do I create a Monitor View for the Order flow?

What Monitoring is

Nodinite monitors all links as Resources in the integration chain. You receive alerts and resolve issues proactively with true end-to-end monitoring.

Why Monitoring matters

With integrations spread across on-premise and cloud systems, you need to identify and resolve issues quickly. Nodinite lets you interact with all monitored Resources in one place, streamlining operations and reducing complexity.

How Monitoring works

Nodinite supervises and interacts with monitored Resources using Monitoring agents.

Repository Model

Documented solutions are key to personal independence

How to use the Repository Model

Nodinite provides documentation as a CMDB feature called the Repository Model. Nodinite Administrators or repository contributors manage the Repository Model as your single source of truth.

Feature Description
Monitor Views Access documentation instantly—no more searching
Alerts Get the information you need to resolve issues or create well-defined tickets
Log Views Easily identify which Integration logged each event
Knowledge base Articles Access related articles and user guides directly from Monitor Views
Integration Landscape Visualize your integration landscape with drag-and-drop entities for a holistic overview
End-user perspective Administrator perspective
How do I know how many Integrations I have? How do I create and manage Integrations?

What the Repository Model is

Nodinite defines common system integration entities in a standard way, creating a unified representation that fits all integration platforms.

Why the Repository Model matters

With integrations distributed across on-premise and cloud systems, you often find documentation fragmented. Nodinite lets you document everything in one place, reducing complexity and increasing independence.

How the Repository Model works

Nodinite includes built-in administration for managing the Repository Model. Developers automate documentation using the Web API as part of their DevOps routines.

Next Steps