Request a demo

Sentry features

Monitor every infrastructure layer in one incident context.

Bring together live connectivity checks from service response and physical devices to server ports and 802.1X/MAB validation. See the changing state, then decide where to start using related syslog records and AI-assisted review.

End-to-end visibility

Know what you monitor, layer by layer.

Each check answers a different question. Sentry keeps reachability, port, protocol, and authentication results distinct, then brings their signals into a shared timeline when an incident occurs.

  1. 01 HTTP · HTTPS · REST · WebSocket · MQTT

    Service monitoring

    Check whether the digital service used by a customer or business workflow is actually responding.

    • HTTP / HTTPS responses and REST endpoints
    • WebSocket connection continuity
    • MQTT broker connectivity and subscription response
  2. 02 ICMP · TCP port · Subnet

    Network and port level

    See whether the device is reachable and whether the required TCP port is open and responding.

    • Reachability with ICMP (Ping)
    • TCP port connectivity checks
    • Subnet discovery and topology context
  3. 03 SNMP · Syslog · Discovery

    Hardware monitoring

    Track switches, access points, firewalls, and other supported network devices with inventory and status context.

    • Device discovery and approved inventory
    • SNMP-based status information
    • Grouping by device and category
  4. 04 Ping · SSH · TCP port

    Server monitoring

    Separate access to a physical or virtual server from the state of the services running on it.

    • Server reachability
    • SSH and defined port checks
    • Correlation between server and service incidents
  5. 05 802.1X · MAB · RADIUS

    802.1X and MAB validation

    Sentry actively tests 802.1X authentication; review failures and delays alongside RADIUS responses and related records.

    • Active 802.1X authentication flow test
    • MAB validation result
    • Response time, timeout, and rejection distinction
  6. 06 SSL/TLS · Domain · Notification

    Certificates and domains

    See time-related outage risk for working services before renewal is due.

    • SSL/TLS certificate expiry date
    • Domain renewal date
    • Early warning by days remaining

Support for a specific device, vendor, metric, or validation flow is confirmed for your environment before setup.

HOW SENTRY COLLECTS EVIDENCE

It doesn’t just wait. It tests.Queries. Listens. Interprets.

Sentry actively performs 802.1X authentication tests and checks devices and services using their own methods. It merges different findings into one incident context, then uses AI to focus the investigation.

ACTIVE TEST

Can a client actually authenticate to the network?

Sentry actively tests the authentication flow, distinguishing success, rejection, timeout and latency.

DEVICE QUERY

What state does the device report?

Queries supported devices for status and interface information, combining reachability with the device’s reported state.

RECORD INTAKE

What did devices and services record?

Receives event records sent by sources. It is not an active reachability test; it adds time and event context alongside checks.

ACTIVE TEST

Is the target reachable over the network?

Checks reachability with Ping. A reachable target does not by itself confirm that its application is healthy.

ACTIVE TEST

Does the application respond to a request?

Sends a request to an HTTP endpoint, tracking service response and latency separately from network reachability.

ACTIVE TEST

Does the secure endpoint respond?

Checks service responses over HTTPS; certificate monitoring adds context for access issues and time-related risks.

ACTIVE TEST

Can the messaging service be reached?

Checks MQTT broker connectivity and configured subscription responses, distinguishing field connectivity from the messaging layer.

ACTIVE TEST

Does the required port accept connections?

Attempts a connection to a configured TCP port. Reads port access alongside device reachability and application response.

01

Each method asks a different question.

Active checks test access and service behavior; SNMP queries device information, while Syslog receives records sent by sources.

02

Separate results. One incident context.

Findings are read together using target, time and infrastructure relationships. Sources and results stay distinct; one check does not substitute for another.

03

Not a status list. An investigation direction.

AI summarizes related findings and suggests possible causes and checks. Verification and intervention decisions remain with your team.

FINDINGS READ TOGETHER

  • 802.1X · timed out
  • ICMP · target reachable
  • Syslog · access record

Sentry AI

The target is reachable, but authentication does not complete. Review the authentication service and policy match alongside access records first.

VALUE FOR YOUR TEAM

Separate device reachability from a user’s ability to join the network.

FINDINGS READ TOGETHER

  • SNMP · interface finding
  • ICMP · device reachable
  • Syslog · link record

Sentry AI

The device remains reachable while an interface finding changes. Review the related link and records from the same time window together.

VALUE FOR YOUR TEAM

Start with the affected connection, not just whether the device is up.

FINDINGS READ TOGETHER

  • Syslog · application error
  • HTTP · no response
  • ICMP · server reachable

Sentry AI

Application errors and lost service responses occur in the same window. Since network access remains available, review the application layer first.

VALUE FOR YOUR TEAM

Put what was recorded at the time next to the alert.

FINDINGS READ TOGETHER

  • ICMP · target reachable
  • TCP port · connected
  • HTTP · no response

Sentry AI

Network access and port connectivity are available, but HTTP does not respond. Review service behavior and application records instead of general reachability.

VALUE FOR YOUR TEAM

Separate network access from service health.

FINDINGS READ TOGETHER

  • HTTP · no response
  • ICMP · server reachable
  • Syslog · service error

Sentry AI

The server is reachable, but HTTP does not respond. Related service errors support reviewing application state and recent changes.

VALUE FOR YOUR TEAM

See the response of the service your customer uses, not just the server.

FINDINGS READ TOGETHER

  • HTTPS · response issue
  • TCP port · connected
  • TLS · certificate finding

Sentry AI

Port connectivity succeeds, but the secure service response has an issue. Verify TLS findings and service configuration together.

VALUE FOR YOUR TEAM

An open port and a working secure service are not the same thing.

FINDINGS READ TOGETHER

  • MQTT · connection issue
  • ICMP · broker reachable
  • Syslog · broker record

Sentry AI

The broker is reachable over the network, but MQTT connectivity has an issue. Review the broker service and related connection records.

VALUE FOR YOUR TEAM

Investigate silent field data in the context of the messaging layer.

FINDINGS READ TOGETHER

  • TCP port · not connected
  • ICMP · target reachable
  • Syslog · service record

Sentry AI

The target is reachable, but the configured port does not accept connections. Verify the listening service and access rules.

VALUE FOR YOUR TEAM

See the closed service door even when the device is up.

All monitoring features

THERE ARE PEOPLE BEHIND THE TECHNOLOGY

You monitor a port.It affects a working day.

Sentry examines the technical layer of a connection; your team sees what that connection means for a store, a guest or a production line.

Store employee and IT specialist reviewing a checkout terminal in a bright shop
AI-generated illustrative field scene 01 / SENTRY

“It’s not just a transaction waiting at checkout.”

When the payment service stops responding, the customer experiences a wait. Your team needs to know where to start.

  • ICMP
  • HTTPS
  • Syslog
  1. TECHNICAL FINDING

    The server is reachable; the payment endpoint is not responding.

  2. AI-ASSISTED REVIEW

    Service responses and records from the same window support reviewing the application layer first.

  3. BUSINESS CONTEXT

    Store and IT teams discuss the same incident context and start at the relevant layer.

Let’s discuss our own scenario
Receptionist and IT specialist discussing access issues in a bright hotel lobby
AI-generated illustrative field scene 02 / SENTRY

“Wi-Fi connected. The guest still can’t get online.”

A wireless connection icon does not confirm completed access. Read the guest’s issue alongside the authentication process.

  • 802.1X
  • SNMP
  • Syslog
  1. TECHNICAL FINDING

    The network device is reachable; the active authentication test times out.

  2. AI-ASSISTED REVIEW

    The authentication service and policy match can be checked alongside related access records.

  3. BUSINESS CONTEXT

    The reception report gains a technical investigation direction; the team separates access from authentication.

Let’s discuss our own scenario
Production supervisor and field IT specialist reviewing a network cabinet beside a production line
AI-generated illustrative field scene 03 / SENTRY

“The line is running. Why isn’t the data arriving?”

Physical production can continue while a silent sensor connection leaves the tracked process out of sight.

  • MQTT
  • SNMP
  • ICMP
  1. TECHNICAL FINDING

    The target is reachable; the MQTT connectivity check reports an issue.

  2. AI-ASSISTED REVIEW

    Messaging service and related network interface findings can be reviewed together to focus the next check.

  3. BUSINESS CONTEXT

    Production and IT teams assess the same connection through shared findings, not separate screens.

Let’s discuss our own scenario

Access validation visibility

In 802.1X and MAB tests, see not only the outcome but where the wait occurs.

Sentry does not just listen to access records; it actively performs 802.1X authentication. Review the RADIUS response, rejection or timeout, and measured latency in the same test record.

  • Separates success, rejection, and timeout outcomes
  • Records measured latency with test time and target context
  • Brings related syslog records into the same time window for review

Sentry does not declare a definitive root cause. It ranks possible issue points based on evidence; verification and intervention remain with the team.

Illustrative validation test — not live data

Review required

Connectivity
Reachable
RADIUS response
Delayed
Validation
Timed out

Evidence-led investigation direction

Network connectivity is available, but validation does not complete within the expected window. Review the RADIUS service, policy match, and access records from the same time window in order.

One incident, four layers

Keep the relationship from hardware to service intact.

Read an alert with its connected infrastructure layers, not in isolation.

  1. 01

    Hardware

    Inventory, reachability, and status signals for physical and virtual targets.

  2. 02

    Network and port

    Subnet, topology, connectivity, and service-port checks.

  3. 03

    Server and service

    Separate evaluation of server access and application response.

  4. 04

    Incident and insight

    Guided review using live checks, syslog, and historical records.

Demo request

Get in touch

Tell us about your environment and the targets you want to monitor; let's work out the right setup method and pricing together.

A monitoring plan that fits your needs

  1. 01Number of targets to monitor
  2. 02Check types and frequency
  3. 03Usage needs

Email: sales@mintyfi.com

Leave your details

We use cookies for visit statistics. Cookie policy