Getting started

This guide walks you through creating your account, getting an API key, sending your first logs, and verifying that they reached LogInformant.

1 Create your account

Head to app.loginformant.com and create your account. The Free tier gives you 1 application, 1,000 logs per day, 7-day retention, 1 GB storage, and 1 team member.

Important: card verification is required before the Free tier can ingest logs.
2 Create an application

After signing in, click Add Application and name it after the service you want to monitor. LogInformant generates environment-specific API keys so you can keep development and production traffic separated.

3 Copy the API key for the right environment

Each application exposes one or more API keys depending on its environment setup. Copy the exact key for the environment you are wiring up and keep it in a secret store or environment variable.

Tip: never hardcode the API key in source control. Use environment variables, a secret manager, or your deployment platform's secure configuration system.
4 Install the package for your stack
5 Verify the ingest path

Start your application, trigger a few logs, then open the dashboard and search for the events from your application. If your tier includes real-time streaming, you can also use the live stream view.

  • Confirm the API key belongs to the same application and environment you configured.
  • Confirm the API URL is https://app.loginformant.com.
  • Confirm your network allows outbound HTTPS on port 443.
  • If you are on Free, confirm card verification has been completed before expecting ingestion.

What happens to your logs?

Logs are stored under your account, indexed for search, and retained according to your current plan. You can remove application data from the dashboard when you need to clean up or reset a project.

Next steps

  • Move to Serilog, Winston, or the guide for your preferred stack.
  • Review pricing if you need advanced search, export, real-time streaming, custom dashboards, or AI log analysis.
  • Use alert rules and Slack integration after you have a reliable baseline of events coming in.