Requesting New Features and Providing Feedback

We love hearing from our customers! Your feedback and feature requests play a vital role in shaping Server Scout's development. Whether you've identified a gap in functionality or have an idea for improvement, we want to hear about it.

How to Submit a Feature Request

The best way to request new features is through our support system:

  1. Create a support ticket at app.serverscout.ie
  2. Select "Feature Request" as your ticket category
  3. Describe the feature you'd like to see implemented
  4. Explain the problem it would solve or how it would improve your workflow

Our AI support bot will acknowledge your request immediately, and the development team reviews all feature requests regularly.

What to Include in Your Feature Request

To help us understand your needs and evaluate feasibility, please include:

Clear Description

Explain what functionality you'd like to see. Be as specific as possible about what the feature should do and how it should behave.

Use Case Context

Tell us about your monitoring environment and workflow. Are you managing web hosting servers, database clusters, or development environments? This context helps us understand how the feature fits into real-world scenarios.

Problem Statement

Describe what challenge you're currently facing or what inefficiency the feature would address. Understanding the underlying problem sometimes leads to better solutions than originally envisaged.

Your Vision

Share how you imagine the feature working. Would it be a new dashboard section, an alert type, or an integration? Your perspective helps us design features that match user expectations.

How Feature Requests Are Handled

We take a systematic approach to evaluating feature requests:

Review Process

The development team reviews all incoming feature requests. We read every suggestion, even if we can't respond individually to each one immediately.

Frequency Analysis

We track how often similar features are requested. Features that solve common problems naturally receive higher priority in our planning process.

Technical Evaluation

Each request undergoes technical feasibility assessment. We consider how well it aligns with Server Scout's lightweight philosophy and whether it can be implemented without compromising performance.

Roadmap Integration

Features that pass initial evaluation are considered for inclusion in our product roadmap, weighing factors like development effort, user impact, and strategic fit.

Beyond Feature Requests

Bug Reports

If you've encountered unexpected behaviour or errors, please use the "Bug Report" category instead. Include details about your system, the steps that led to the issue, and any error messages you've seen.

General Feedback

Have thoughts about the user interface, documentation, or overall experience? We welcome this feedback through any ticket category. Your insights help us improve every aspect of Server Scout.

Documentation Suggestions

If you've found gaps in our knowledge base or areas where instructions could be clearer, let us know. Good documentation is crucial for a positive monitoring experience.

Setting Realistic Expectations

Whilst we carefully consider every feature request, we cannot implement all suggestions. Our focus remains on:

  • Features that benefit the most users rather than highly specific edge cases
  • Maintaining simplicity and avoiding feature bloat that could complicate the user experience
  • Preserving performance and our lightweight footprint
  • Ensuring reliability by not rushing complex features to market

Some requests may be declined if they conflict with these principles, but we'll always explain our reasoning when possible.

Your Voice Matters

Feature requests directly influence Server Scout's development direction. Many features you use today started as customer suggestions:

  • Multi-user access came from hosting companies needing team collaboration
  • Device monitoring via SNMP emerged from requests to monitor network infrastructure
  • Various alert thresholds were refined based on real-world monitoring needs

Your feedback doesn't just improve the product—it helps create a monitoring solution that truly serves the Linux server community.

Ready to share your ideas? Create a support ticket today and help shape the future of Server Scout!

Frequently Asked Questions

How do I submit a feature request to ServerScout?

Create a support ticket at app.serverscout.ie and select 'Feature Request' as your ticket category. Describe the feature you'd like, explain the problem it would solve, and provide context about your monitoring environment. The AI support bot will acknowledge your request immediately and the development team reviews all requests regularly.

What should I include in my ServerScout feature request?

Include a clear description of the functionality, your use case context (web hosting servers, databases, etc.), a problem statement explaining what challenge you're facing, and your vision of how the feature should work. Being specific about your monitoring environment and workflow helps the team understand real-world application.

How does ServerScout evaluate feature requests?

ServerScout uses a systematic approach including review by the development team, frequency analysis to track common requests, technical feasibility assessment, and roadmap integration. They prioritize features that benefit most users while maintaining simplicity, preserving performance, and ensuring reliability.

Why might my feature request be declined?

Feature requests may be declined if they conflict with ServerScout's core principles of serving the most users, maintaining simplicity to avoid feature bloat, preserving performance and lightweight footprint, or ensuring reliability. The team focuses on features that benefit the broader user base rather than highly specific edge cases.

Can I report bugs through the same system as feature requests?

No, use the 'Bug Report' category instead of 'Feature Request' for unexpected behavior or errors. Include details about your system, steps that led to the issue, and any error messages. This helps the team distinguish between new feature needs and existing functionality problems.

Have customer feature requests actually been implemented in ServerScout?

Yes, many current ServerScout features originated from customer suggestions. Multi-user access came from hosting companies needing team collaboration, device monitoring via SNMP emerged from requests to monitor network infrastructure, and various alert thresholds were refined based on real-world monitoring needs from users.

What types of feedback does ServerScout accept besides feature requests?

ServerScout welcomes general feedback about the user interface, documentation, or overall experience through any ticket category. They also accept documentation suggestions if you find gaps in their knowledge base or areas where instructions could be clearer, as good documentation is crucial for positive monitoring experience.

Was this article helpful?

Related Articles