Remote logging with Flutter on the ELK stack

Marc Logemann
Oct 22, 2019 · 5 min read
Image for post
Image for post

Letting your Flutter applications log in the cloud is a very good idea when it comes to beta test software within a closed user group. Here you want as much information about your app behaviour as possible. Having no access of the user devices log system in fact requires a cloud based application to log into. Furthermore you want a system where you can easily search your log content and submit tags like userId on each log statement.

The ELK stack of

The company offers an easy to integrate logging system with full search capabilities with the help of Kibana, Elasticsearch and Logstash. Apart from doing searches via their nice User-Interface, you can also do a Live-Tail, which is exactly what its name implies, a web based tail on all your logging actions. This is super nice and the delay is definitely acceptable.

They integrate with lots of framework and languages, which you can easily search via their Log Shipping menu item in the console. Unfortunately there is no easy way for flutter described, but luckily there is a package for a dart based logging system:

The mentioned package only contains appenders for the base logging system, which is also available at at:

But lets create an account first…

Image for post
Image for post
Register Screen at
  • head over to and click “free trial” (there is free package available after trial if you don’t need the pro features)
  • fill out the form and have an eye on the region selection (on the left us-east-1 AWS is selected). To be sure which region you have chosen, copy it to your notepad or the likes cause you will need that information later on when connecting the client library to the service.
  • After logging in to your account, go directly to the preferences icon on the upper right corner and select Settings -> General
  • Write down the Token value unter the section Account Settings.

This is all we need to do on the side of things. Let’s continue with the configuration in Flutter.

Integrating the service

As mentioned above, there is already a nice little package which helps us connecting to the service of Basically it uses the Bulk Data REST API of to push the data to the logging system. Configuring the appender is a bit tricky because the default URL works only for a certain zone, so chances are high that you have selected a different one upon registration and fail to connect.

So lets start by adding the two needed packages in the pubspec.yaml:

logging: ^0.11.3+2
logging_appenders: ^0.2.2

After doing flutter packages get you will have the package available in your project. Now lets write real quick a simple Hello LoggingWorld application:

import 'package:flutter/material.dart';
import 'package:logging/logging.dart';
import 'package:logging_appenders/logging_appenders.dart';

createLogger() {
Logger.root.level = Level.ALL;

url: "",
labels: {
"version": "1.0.0", // dynamically later on
"build": "2" // dynamically later on

void main() {

class MyApp extends StatelessWidget {
final _logger = Logger('com.example.helloLogging');

Widget build(BuildContext context) {
return MaterialApp(
title: 'Welcome to Flutter',
home: Scaffold(
appBar: AppBar(
title: Text('Welcome to Hello LoggingWorld'),
body: Column(
children: <Widget>[
child: RaisedButton(
child: Text("Log '123' on Info"),
onPressed: () {"123");
child: Text("Log '456' on severe"),
onPressed: () {

Let’s go through the important lines in this code.

The parameters to LogzIoApiAppender are of course the most important part to get the connection going.

  • apiToken -> The token you have written down from the preferences account menu. So replace <ACCOUNT_TOKEN_FROM_SETTINGS_GUI> with your actual token.
  • url -> This largely depends which region you selected during registration. The example code uses West Europe (Netherlands), Azure. Use the following table to get the host of the url for your selected region: —> US East (Northern Virginia), AWS —> Asia Pacific (Sydney), AWS —> Canada (Central), AWS —> Europe (Frankfurt), AWS —> West Europe (Netherlands), Azure —> West US 2 (Washington), Azure
  • labels are kind of meta data for every logging statement. Its wise to use at least the version of your app or you could supply a userId after login to pinpoint problems in your software later on.
Image for post
Image for post

Lets start the HelloWorld Logging app

So when you start the application, you will see two buttons which will basically log to the system. But before you start clicking those, you want to login the console, click on the LiveTail tab and (important!) also click on the play button to start the tail.

When you push the buttons in the app, after some seconds delay, you will see the log statement appear. If you want to search for log statements you need to head over to the Kibana tab and click discover in the menu.

For sure you can do a lot more with this ELK stack but this wont be the scope of this article. I am pretty sure the nice folks at will help you out if you want to know more.

Disclaimer: I dont work for LogHero Ltd., the company behind It just happened that i searched for a nice solution and the logging_appenders package brought me to

If you want to know more about well architected cloud applications on Amazon AWS or how to use Flutter with Firebase, feel free to head over to for more infos or reach me at the usual places in the internet.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium