Being among the first to be notified when tickets go on sale online for events with high demand is paramount if you hope to secure tickets. Given the lucrative Secondary Market that’s emerged for event tickets (especially for concerts and sporting events), it’s become increasing difficult to acquire tickets for these popular events.
With the newest updates to the StatusCake app you are now able to get a lot more done whilst on the go. We’ve added several features which we think will enhance the experience, and there’s a lot more to come over the next few weeks, so keep your eyes peeled!
This year at Sensu Summit, Fletcher Nichol and I gave a talk on systems architecture entitled Pull, don’t push: Architectures for monitoring and configuration in a microservices era. In this post, I’d like to reiterate and expand on some of the concepts in that presentation and make some more concrete recommendations for systems design in an era of complex distributed systems.
Eating your own dog food is a concept also referred to as dogfooding. This is when a company uses its own product which was made famous by Google and Microsoft who employ the tactic to test their products in real-world usage. Dogfooding can act as quality control, and can also be a kind of testimonial advertising. For leaders, it’s a way to truly understand what you have, help you set your future direction and understand the challenges your team face on a day to day basis.
In Elasticsearch parlance, a document is serialized JSON data. In a typical ELK setup, when you ship a log or metric, it is typically sent along to Logstash which groks, mutates, and otherwise handles the data, as defined by the Logstash configuration. The resulting JSON is indexed in Elasticsearch.
It might surprise you that the version of cron that runs on your server today is largely compatible with the crontab spec written in the 1970s. One downside of this careful backwards compatibility is that jobs, even on the same server, can be created and scheduled differently.
First, an introduction. My name is Matt Yonkovit. In September, I joined Mattermost as the head of Customer Success. For the last 13 years, I’ve helped customers succeed using open source software. My goal at Mattermost is to build out a world-class support and success program that enables our customers and community to use Mattermost to revolutionize their business processes and workflow.
In the past, applications would be deployed by installation on a host, using the operating system package manager. This was a heavy solution with tremendous reliance on the operating system package manager and increased complexity with libraries, configuration, executables and so on all interconnected. Then came containers. Containers are small and fast, and are isolated from each other and from the host.
This recipe is similar to the previous rsyslog + Redis + Logstash one, except that we’ll use Kafka as a central buffer and connecting point instead of Redis. You’ll have more of the same advantages.
Starting from Elasticsearch 5.0, you’re able to define pipelines within it that process your data, in the same way you’d normally do it with something like Logstash. We decided to take it for a spin and see how this new functionality (called Ingest) compares with Logstash filters in both performance and functionality. Is it worth sending data directly to Elasticsearch or should we keep Logstash?
