Company: Enix.io
Industry: DevOps and Cloud Native technologies
Location: France
Number of employees: 18
Year of integration: 2019
Number of Amixr Users: 6
Amixr Integration
Integration: Slack
Monitoring stack: Prometheus, AlertManager, Observium, and Statuscake

What we love the most about Amixr is that it’s very low maintenance and has been extremely reliable for us.

Enix is a cloud and IT infrastructures company, with a special and well recognized expertise in DevOps and Cloud Native technologies: containers, Kubernetes, CI/CD, GitOps, infra-automation, etc.

We help companies to adopt these new technologies by providing end-to-end services: training, audit, design, deployment, hosting, and day-to-day operations. We are particularly proud of our first-class 24/7 operation service, using modern and cloud-native monitoring systems.

With 15 years of experience, we can manage all types of infrastructure needs: servers, virtualization, storage, container stack, database, network, security, etc.

We can deploy customer’s service platforms on Enix infrastructures, On-Premises, main public and private Clouds, or hybrid.

In several words, Enix aims to provide comprehensive and long-term support to dev and DevOps teams. We manage their software factory and their automation tools, we design and operate their platforms in production: this way, they can focus on their core business activities.

Why is incident management monitoring important? How does uptime impact your business and customers?

An important part of our business at Enix is to handle the operations of managed services on either our or our client’s infrastructure 24 hours a day, 7 days a week, 365 days a year. Uptime and a quick reaction time are fundamental. We need to be aware as soon as possible when something is wrong so we can restore service quickly while protecting the sanity of our staff’s work-life balance.

What’s your monitoring stack? Did it evolve after you integrated Amixr?

We use Prometheus and AlertManager for system and service monitoring. We use Grafana for visualization, ObserviumNMS for network equipment like switches and routers, and Statuscake for “out-of-band” external monitoring or http(s) uptime monitoring.

What did incident response look like for dxFeed before you integrated Amixr?

During office hours, we look at the ceiling here .

Before integrating Amixr, we were pushing alerts and the escalation process through emails and Slack channels. A lot of people were involved during each incident. We were also using Jira Service Desk for inbound customer emails.

How did you choose incident management? What qualities are important to you?

Amixr stood out because of its Slack integration and escalation process with the ability to use SMS and calls as necessary. It was very easy to integrate with various alerting sources thanks to JSON templating and the pricing was exactly within our budget.

Tell us about your Amixr onboarding process. How much time did it take? How would you describe your experience? What was cool and what wasn’t? Did the system meet your expectations?

It was incredibly smooth. While the product was quite new, the documentation was already very useful. I set up a trial account and had our Prometheus AlertManager and Observium NMS sending alerts to Amixr without interfering with our old process. The Amixr team was also very quick and helpful in answering our questions and responding to the suggestions we sent via email. Once my partners saw how easy Amixr was to integrate, everyone was on board.

How did you configure the system and workflow? Which practices do you use? What would you like to improve? What’s the best monitoring or incident management case that occurred while using Amixr?

We currently have approximately six users frequently watching the alert-mixer. We created three integrations in the Amxir Slack app: AlertManager, Observium, and Statuscake. These integrations receive only “critical” alerts. Warnings are sent to another Slack channel and are not managed by the alert-mixer. All Amixr integrations send messages to a single #alert-mixer channel watched by those users.

We have both basic routing and escalation for critical alerts with different escalation steps. Slack highlight is the first step; then, if Slack is unacknowledged, it alerts by SMS 30 minutes later. If the SMS is unacknowledged, it alerts by phone call after 30 minutes.

The feature we would like to see added is the ability to quickly silence a Prometheus AlertManager issued alert for a configurable duration directly from the Amixr Slack alert message.

What we love the most about Amixr is that it’s very low maintenance and has been extremely reliable for us.


Who do you want to suggest Amixr to?

Every customer we have that uses Slack might be interested in Amixr’s many features.

What would you like to say to the Amixr team?

Thank you for such a great product. It really helps us in our day-to-day operations!❤️️