Log Streaming with Frontegg

Part of our journey in helping ease the pain of developing applications has been the expansion of our integrations with other popular managed-service providers. This is especially relevant with log streaming. Log streams not only give us insights into how well products are doing but they can also be used to highlight areas of improvement. We recently added two more log streaming integrations to our console: AWS EventBridge and Splunk.

What is Log Streaming?

First and foremost, what exactly is log streaming? Log streaming is the ability for Frontegg to save logs with a third-party data analysis tool in near real-time. In this way, teams are able to have a centralized view of the events related to and the health of their application(s). Log streaming, especially for an identity provider like Frontegg, is crucial because it generates valuable logs that offer deep insights into user behaviors and system performance. These logs provide developers with a live view of user login attempts, successful authentications, and security related events. This provides companies the data necessary to enhance security, understand their user engagement, and troubleshoot issues with their application.

What’s Involved?

Regardless of whether you’re using EventBridge or Splunk, the setup is going to be similarly easy.

At a high level, we only require the endpoint names and credentials for accessing these services. In the case of EventBridge, you will need your access key and secret key that you created in the AWS console as well as some more information regarding the event configuration.

With Splunk, you’ll need the host, port, and HEC token. It’s as simple as entering these values in your Frontegg account to get started. Once you have completed this, you will now be successfully streaming all of our logged events. These will include both successful and unsuccessful attempts to perform actions related to your Frontegg account such as logins, email verifications, or when someone has been locked out due to rate limiting.

So Why Use Log Streaming?

The logs from your identity provider allow you to make better decisions about the development and security of your application. Authentication is often the first step to users meaningfully interacting with your product. This means that the logs from these transactions are likely the first step into understanding more about who your users are. Whether that be learning more about where they are logging in from to what hardware they are using to access your application, these insights are all logged events that you can emit directly from your Frontegg account to your log streaming service. Additional built-in features like anomaly detection will also appear in your log stream so that you will know as soon as we do about potential malicious activity affecting your accounts. This will help your team better tailor the allocation of resources in response to who your customers are and how they interact with your application. Along with accelerating development, log streaming may also be a requirement for your application to be in compliance with your industry’s security standards.

Easing the Development Journey

Our logged events and log streaming integrations have one goal in mind: easing the journey for all developers – whether it’s migrations, compliance, or new functionality. Easily add critical real-time auth insight into your applications.