Dependency Auto-Discovery System

The Auto-Discovery System is Pulsimo's intelligent feature that automatically detects relationships between your services without manual configuration. It analyzes your infrastructure and suggests dependency connections based on proven patterns and industry standards.

What is Auto-Discovery?

Auto-Discovery is like having an AI assistant that watches your infrastructure and says:

"Hey! I noticed your Backend service talks to that Redis instance on port 6379. Should I track that as a dependency?"

Instead of manually configuring every dependency relationship, Pulsimo automatically finds them and asks for your approval.

How It Works

1

Continuous Scanning

Pulsimo analyzes all your registered services, looking for patterns, ports, and naming conventions

2

Pattern Matching

Applies smart detection rules based on port numbers, service names, and URL patterns

3

Confidence Scoring

Each discovery gets a confidence score from 70% (uncertain) to 95% (very sure)

4

Your Approval

Pulsimo shows you the discoveries. You approve ✅ or reject ❌

5

Automatic Tracking

Approved dependencies are tracked and health monitoring begins automatically

What Can Be Auto-Discovered?

1. Cache Layers 💾

Redis Detection90-95%
  • ✓ Port 6379 in URL
  • ✓ "redis" in service name
  • ✓ redis:// URL scheme
Memcached Detection85-90%
  • ✓ Port 11211 in URL
  • ✓ "memcache" in name

2. Search Layers 🔍

Elasticsearch90-95%
  • ✓ Port 9200 (HTTP API)
  • ✓ Port 9300 (transport)
  • ✓ "elastic" in name
Apache Solr85-90%
  • ✓ Port 8983 in URL
  • ✓ "solr" in service name

3. Database Layers 🗄️

PostgreSQL
Port 5432
95%
MySQL/MariaDB
Port 3306
95%
MongoDB
Port 27017
95%

4. Message Queues 📨

RabbitMQ
Ports 5672, 15672
90%
Apache Kafka
Ports 9092
90%

Confidence Score System

Every discovered dependency gets a confidence score (0-100%) indicating how sure Pulsimo is about the relationship.

🟢Very High
95-100%
Safe to auto-approve
🟢High
85-94%
Review and approve
🟡Medium
75-84%
Verify before approving
🟡Fair
70-74%
Double-check carefully

User Interface

Location: Dashboard → Dependencies → Auto-Discovery Tab

✨ Auto-Discovered Connections

Found 5 same-project dependencies
Review and approve to add them
NodeJsProjectsHigh93%
NodeJsDemoBackend
backend
RedisSessionCache
cache
Detection:
Redis default port detected

Using Auto-Discovery

Reviewing Discoveries

  1. 1
    Access Auto-Discovery
    Go to Dashboard → Dependencies → Auto-Discovery tab
  2. 2
    Review Each Discovery
    Check service names, confidence score, and detection reason
  3. 3
    Take Action
    Approve individual, reject, or bulk approve high confidence discoveries

Smart Features

Same-Project Filtering

Auto-discovery only suggests dependencies within the same project to prevent cross-project noise and focus on relevant relationships.

Duplicate Prevention

Won't suggest dependencies that already exist. Checks before every scan to keep suggestions clean and relevant.

Confidence-Based Sorting

Discoveries are shown highest confidence first, making it easy to approve the most certain ones quickly.

Auto-Expiration

Unverified discoveries older than 30 days are auto-removed to prevent stale suggestions and keep the list fresh.

Best Practices

For DevOps Teams

  • Run discovery after infrastructure changes
  • Review discoveries weekly
  • Use naming conventions for better detection

For Platform Engineers

  • Audit approved dependencies monthly
  • Monitor confidence trends
  • Document custom dependencies manually

Frequently Asked Questions

Q: Does auto-discovery run automatically?
A: Yes, it runs every 5 minutes in the background. You can also trigger manual scans anytime.
Q: Will it suggest cross-project dependencies?
A: No, only same-project relationships are suggested. Cross-project dependencies must be added manually.
Q: What happens if I reject a discovery by mistake?
A: Click "Scan for More" to regenerate discoveries, or add the dependency manually.
Q: Can auto-discovery detect custom ports?
A: If the service name contains the technology name (e.g., "CustomRedis"), it will be detected even on non-standard ports.

Related Documentation