Martello BLOG : 2017

The agent-based monitoring strategy that your MPA system uses to collect performance data has several advantages, including dependable security and access to more detailed performance information about the devices on your network. In MPA, the probe is the hub for all data collection – without it, MPA can’t report on the KPIs you need, like availability, utilization and voice quality.

For most, probe installation is often a ‘set it and forget it’ exercise but once set up is complete, what type of attention should you really be paying to your probe? A properly installed probe is the driver for all the key features of MPA: network monitoring, alerts, and data that will keep your customers’ network healthy. If your probe has gone down, it will no longer report the status of the devices it is monitoring to the MPA server.

Probes should ‘check’ into MPA periodically (default time, every 15 minutes), and if that isn’t happening there can be a number of causes. Setting thresholds for your probe will ensure that you receive instant notifications when your probe has stalled. These thresholds can be configured either on a probe individually or apply to all probes that you manage at the Root container level and will apply to all probes at once. Once your thresholds are set, you don’t need to wonder “Is my probe working’. If it isn’t, you will be the first to know with an alarm.
In the Alarm Analytics tab you can see the alarms that have been generated for inactive probes, among other alarms.
Keeping Tabs on Probe Activity - MPA
Below is the Probe’s dashboard, where you can see if your probe is active. This is a screenshot of a ‘healthy probe’ that is checking in regularly. If the timespan to check in exceeds the set limit of fifteen minutes, an alarm will be generated.
Keeping Tabs on Probe Activity - MPA
In MPA there is a ‘master view’ of all the possible thresholds that you can set for monitored devices. Under “Probe Check-in” you can configure the threshold for your probe.
Keeping Tabs on Probe Activity - MPA

In the threshold configuration window you can set a threshold for your probe.

Without a functioning probe, you lose valuable report device data that is fed into MPA. Taking the easy step of setting up thresholds for your probes is the key step in monitoring your customers’ network more efficiently. Need help? Contact our Customer Success Specialist.

As summer folds into fall and the kids head back to class, we can’t help but get caught up in the back to school excitement. At Martello, welcoming new co-op students has become second nature to us by now and we eagerly anticipate the exchange of ideas, opportunities to push the boundaries of design that comes along with these bright and enthusiastic additions to the team. Martello’s Co-Op Program is part of our long-term strategy to recruit terrific talent and enhance the Martello community.

Inside Martello, we have built a mentoring program that guides our co-ops along the path to becoming top software designers. This apprenticeship model is one that works at Martello and allows co-ops to forge bonds within the company as they gain practical skills. Our co-op students thrive in our open and welcoming environment.  Fellow Martellians look out for them on the educational front and include them in weekly badminton games and at the infamous ‘co-op shawarma challenge’ that takes place at the end of every placement. Our co-ops are treated like one of the team from day one, running some of the development team’s daily stand up meetings and showing off what they are working on in weekly demo days. We aren’t interested in giving our co-ops ‘busywork’ – the features our co-ops have developed over the years are used every day in more than 5,000 networks around the world.

Welcome to the Martello Team Yahya Rafiyev

Martello Co-Op CultureLast week, we welcomed Software Designer Yahya Rafiyev from the University of Waterloo, where he has completed his third year of studies doing a bachelor’s degree in Computer Science. Yahya’s path to Martello is an interesting one, he grew up in Russia but in his teens returned to Azerbaijan, his family’s original home. When he was in high school, the University of Waterloo came on a recruiting campaign to his school, talking about the opportunities for study in Canada. Because of this, Yahya made the decision to study at Waterloo and to work at Martello.
During his studies at the University of Waterloo, Yahya has had other co-ops at Ericsson and through the University. Yahya chose Martello for this placement because he wanted to hone his software developer skills and felt that he could have more of an impact in a smaller company. He saw lots of opportunity to work on projects that would have real world applications, not just sit on a computer somewhere. He felt that the strong culture at Martello would provide him with the guidance and support that he needed but also give him the chance to build the foundations in order totake intelligent risks and try new things.

“I chose Martello for my co-op placement because I felt that the work I would be doing would have an impact and I was drawn to the strong and supportive learning environment that I knew would be in place here.” said Yahya.

As we help Yahya settle in over the coming weeks, we’re reminded of the impact our Co-Op Program has on our long-term strategy. The investment we make in mentoring our co-ops pays off in many ways – not least the idea that they will some day return to Martello – eventually becoming top software designers within our organization.

Part of The Team: Co-Op Success Story

Martello Co-Op CultureAlok Swamy graduated from Carleton University in 2016 with a degree in Computer Software Engineering and during his studies he completed co-ops at a variety of different companies including Wesley Clover, Recognia, Fuse and Health Canada. In his fourth year, he did a four month co-op at Martello and he thrived in the challenging environment.  Alok says he felt that the team wanted him to succeed, not just for the company but for his own personal development. When he graduated, Alok chose to come back to Martello. Having played a significant part in developing our MarWatch product already, was exciting to him.  Alok had seen that the work he had done was part of a bigger picture – and he wanted to be part of driving our product’s evolution and to be a factor in the success of the company.

“Martello gave me opportunities to grow, develop my skills and take risks that a larger company might not have. I felt that I was doing work that was going to have a significant impact on the product that was being developed.” said Alok “It’s inspiring here, we are not just cranking out boring code. It’s real.”

Every day at Martello we see the impact that our Co-Op Program is having on the company. Everyone from our senior developers to our co-op students see this in action – where employees are encouraged to take intelligent risks, problem solve and think outside the box to solve problems in a supported environment. This is how we work and is the foundation for our corporate culture. As we continue to grow, our Co-Op Program will be a critical part of our success, with a direct impact on the experience our customers have with our product every day.

As the days start to turn cooler here at Martello, we are looking forward to this fall’s launch of Mitel Performance Analytics (MPA) R2.2. With this release, we have packed in a bunch of new features like network diagrams, voice quality visualization and site qualification testing. With fall creeping in and as the kids return to school we thought that you might want to brush up on MPA and see why it has quickly become a standard offering when it comes to delivering reliable network performance.

Tell Me Again…Why MPA?

Managing UC networks is complicated and administrators have to keep an eye on lots of moving parts at one time. It’s important to have a bird’s eye view of what’s happening at all times and grey areas or unknowns on the network are not an option. With MPA, you can clearly visualize the network, quickly identifying issues as they come up but before they impact the end user. MPA delivers the tools you need to get to the root of the problem quickly. Here is a quick primer on ‘why MPA’.
Mitel Performance Analytics Brush Up Back to School
Mitel Specialization with Infrastructure Support – MPA is the only tool that gives you insight into Mitel voice quality and trunk utilization. However, MPA also monitors the status and performance of third-party systems in the network like routers and switches.
Alarms & Analytics –  Real-time alerts give you timely, actionable data on network issues. Alarm analytics ensures that in a sea of data, you see the issues that matter most to you.
Detailed Reports – Reports clearly and concisely demonstrate network and device performance.
Secure Remote Access & Single Sign-On – MPA lets you easily and cost-effectively access network devices anywhere in the world, for more efficient troubleshooting & maintenance. There’s no need for a separate remote access tool when you’re using MPA.
Role-Based Status Dashboards – Whether you’re a channel partner or end user, there’s a dashboard view for you. Well designed dashboards make it easy to identify the most critical issues at a glance and in one straightforward dashboard.
Testing and Site Qualification Tools –  MPA includes tools like Traceroute direct from the handset, making it easier to Identify the source of a problem quickly. UCScore is a web-based tool that tests network fitness for VoIP deployments, to prevent future problems.
Simple Deployment – Whether you’re licensing one device or one thousand, MPA makes it simple to get started and easily add devices with device discovery and bulk device addition
Single Pane of Glass – Since MPA manages performance of the entire network, it can become your single tool for network management. Got a tool you’re already in love with and want to get Mitel-specific monitoring? MPA integrates with other monitoring packages.

Isn’t This Just a ‘Big Network’ Thing?

Partners and service providers are telling us that they are now insisting on MPA when it comes to network monitoring. MPA is no longer reserved for monitoring large or complex networks, its speed-to-resolution is making it a standard offering among our partners.

“There’s a wow factor when you can show customers a problem that they wouldn’t otherwise have detected.” Said Jeff Balch of MXN Corporation. Quickly pinpointing and fixing issues while not eating into key technical resources is critical in today’s economy. When you increase the level of service quality you reduce churn. “Customers are stickier to us with MPA”, said Mike Tavares President, TCS Canada. “Customers are more tech-savvy than ever, and with MPA we have a way to demonstrate quickly where a problem originated, and ensure our first level support techs have it resolved quickly.”

“We’re leveraging MPA more and more…the more we do, the better off all of our customers are.  As they are renewing maintenance, I’m encouraging customers to move onto Premium software assurance at Mitel,  so that we can take full advantage of MPA”. – Mark Compton, Integrated Network Solutions

With MPA, we are continuing to add new features and tools that allow you to quickly identify and resolve problems on the network. In upcoming blog posts we will show you a new place where we are keeping all the MPA resources that you need at your fingertips.