Go to All Forums

List of Feature Requests for StatusIQ / Statuspages

We think StatusIQ is really good! In conjunction with Site24x7 a perfect solution.
If we want to change from our previous Statuspage solution to StatusIQ, then we need some more features at StatusIQ.
It would be great if these things on the following list get on the roadmap.

 

GUI: Responsive Design or native App

 

For On-Call Duty – when you're on the road - the current GUI would be easier to use if a native App for iOS/Android exists or if the GUI is optimized for mobile devices.

 

Events: Incident and Maintenance Templates

 

If it becomes hectic and you do not always know what to write to the customers (subscribers), then templates can help.

 

Events: Additional Coordinator field

 

Especially for internal services it is helpful for the subscribers to know whom they can reach to in case of further questions.

An optional field for the entry of a „coordinator“ would be helpful for incidents and maintenance.

It could also be prefilled with the currently logged in user.

But should be changeable.

 

Components: Hide components from dashboard

 

If a service/component is no longer available for customers or other reasons then an option to hide a component would be helpful rather then delete.

Then we don’t losing all data for a component and we will still have data and metrics available for later reports.

 

Alerting: Third party Integrations

 

It would be very helpful for ops teams if we can also send incidents and maintenance events to Slack and Teams.

 

E-Mail: Domain White List

 

We do not want everyone to be able to subscribe, and a limitation to email domains would be helpful.

 

E-Mail: Custom E-mail signature

 

Adding your own signature to e-mails is also helpful.

 

E-Mail: Custom E-mail text for incidents and maintenance

 

Adding your own greeting text to e-mails is also helpful.

 

E-Mail: Export of all subscribers via CSV

 

Currently only an import is possible. Export as CSV for all subscribers is very helpful.

 

E-Mail: Show event logs for e-mail delivery

 

If customers say they did not receive any messages, a log would be very helpful for analyze.

Logfile should show that E-Mail was successfully sent, bounced or rejected.

 

E-Mail: Test E-mail function

 

To test sending of incident or maintenance events a test function with a custom e-mail address is very helpful.

 

E-Mail: Alerts for notification alerts

 

If you get on a blacklist or there are problems with recipients, an automatic alarm would be very helpful. For example:

 

  • Hard bounces greater than 10% of sent email within a 24 hour period.
  • Soft bounces greater than 10% of sent email within a 24 hour period.
  • Rejected email greater than 10% of sent email within a 24 hour period.

 

Reports: Uptime reports for all or specific services

 

Reports for business units or customers are very helpful in communication.

Monthly Reports for all or specific services (SLA defined) would be helpful.

Or an API exists to get all events with Start/End time, Event Typ and Event Status exists.

 

Others: Google analytics tracking for public pages

 

The integration of Google Analytics for public status pages would be very helpful for later analyses.

 

Thanks,

Torsten

Like (5) Reply
Replies (4)

Re: List of Feature Requests for StatusIQ / Statuspages

Dear Torsten, 

   These are great set of features you have listed for StatusIQ. Thanks for taking the time to list it here. Some of them are already in our roadmap. We'll update this post as and when we have updates. 

-Jasper

Product Manager, Site24x7

Like (0) Reply

Re: Re: List of Feature Requests for StatusIQ / Statuspages

Hello Jasper,

few more things (features).

It happens quite often that a maintenance is announced to customers but Ops forget to put the monitors in Site24x7 into maintenance. This ends up into unnecessary alarms for On-Call duty.
Very nice is already the current possibility to enter the maintenance in Site24x7. This maintenance entry is automatically synchronized according to StatusIQ.
Another great feature would now be the other way around. A maintenance announcement for customers in StatusIQ automatically generates the maintenance settings in Site24x7. So there are no more unnecessary alarms.

Another feature is rather an extension. Currently it is possible to link a component in StatusIQ with a Site24x7 monitor.
However, since it is also possible for a component to consist of several Monitoring Agents, it would be helpful if you could link SEVERAL monitors to ONE component.
In Site24x7 it is also possible to select several monitors for a maintenance entry. In this case currently only ONE monitor is synchronized to StatusIQ. Could this be changed?

And finally a little bug in the completed maintenance window. The menu shows options for incidents. It think this is not wanted here isn't it?

 

Thanks,

Torsten

Like (0) Reply

Re: Re: Re: List of Feature Requests for StatusIQ / Statuspages

Thanks Torsten for adding to your thoughts. Every request that you have asked for makes sense. We will work on bringing out each one of them. 

>>However, since it is also possible for a component to consist of several Monitoring Agents, it would be helpful if you could link SEVERAL monitors to ONE component.

Regarding the above statement, when would you consider the component as down and needs to be communicated to your customers? ex: When there are 5 monitors and 1 components. How would you like us to determine the status of the component. One way to do it is to take a % of down monitors to make the component down. 

 

-Jasper

Product Manager, Site24x7

Like (0) Reply

Re: Re: Re: Re: List of Feature Requests for StatusIQ / Statuspages

Hi Jasper,

good question.

If not all monitors for a component are down then the component could be automatically marked as "partial outage".

% of down monitors seems to be a good option to do this.

Thanks and Regards,

Torsten

 

Like (0) Reply

Was this post helpful?