LogScale's homepage provides a comprehensive overview of repositories, views, and parsers, where repositories store ingested data, views enable cross-repository searching with filtered results, and both can be configured with specific user permissions, dashboards, and saved queries. The system requires all incoming logs and metrics to be processed through parsers (except for structured ingest endpoints), which transform both structured and unstructured text inputs into named fields while preserving the original text in the repository.

LogScale's homepage contains an overview of your views and repositories that you'll use for your ingested data, and the parsers you use to structure it. Views allow you to search across multiple repositories, and can filter your results to a specific subset of data. Both views and repositories can have their own sets of users, all with different permissions, dashboards, and saved queries. To view what's in each repository, click on its title.

Parsers

When sending logs and metrics to LogScale for ingestion, they must be parsed before they are stored in a repository. This is the case for all but LogScale's structured ingest endpoint, which stores data as-is.

Parsers take text as input, which can be structured (like JSON) or unstructured (syslog/application stdout), and puts extracted values into named fields. The original text is also stored alongside the field values in the repository.

To find a list of all parsers, both built-in and custom-built, click on the Parsers tab at the top of the page.

LogScale includes several built-in parsers for your use. For more information and instructions on how to create custom parsers, visit our documentation here: Parse Data