---
name: cloud-logs-agent-multiline-windows
title: Configuring multiline support for the Logging agent for Windows
description: Grouping of multiline logs by the IBM® Cloud Logs Logging agent from non-orchestrated environments (for example, Windows) is configured similar to that of orchestrated environments. The changes include the parsing required to group log lines that are supposed to be together as a single log record.
last-updated: 2025-09-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-logs?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Configuring multiline support for the Logging agent for Windows
{: #agent-multiline-windows}

Grouping of multiline logs by the IBM® Cloud Logs Logging agent from non-orchestrated environments (for example, Windows) is configured similar to that of orchestrated environments. The changes include the parsing required to group log lines that are supposed to be together as a single log record.
{: shortdesc}

If you're running the Logging agent in a non-orchestrated environment (such as a standalone VM or  bare-metal server), you do **not** need to apply multiline parsers using a separate filter or preprocessor.

Instead, you can directly specify your multiline parsers in the `[INPUT]` section of the `inputs.conf` file. This is simpler and sufficient.

For example:

```yaml
[INPUT]
      Name              tail
      Tag               *
      Path              /var/log/*.log
      Path_Key          file
      Exclude_Path      /var/log/audit.log
      DB                /var/lib/fluent-bit/fluent-bit.DB
      Buffer_Chunk_Size 32KB
      Buffer_Max_Size   256KB
      Multiline.parser  go,multiline-java-example,multiline-nodejs-winston
      Skip_Long_Lines   On
      Refresh_Interval  10
      storage.type      filesystem
      storage.pause_on_chunks_overlimit on
```
{: codeblock}

Multiple multiline parsers are specified in `Multiline.parser` as a comma-separated list. The agent will try each parser in the order provided until one matches. This is useful when your system hosts applications with different logging formats (for example, Go, Java, Node.js).

## How multiline logs are grouped for display
{: #agent-multiline-display-win}

When viewing grouped log data in the IBM Cloud Logs UI, the grouped log data is included in the `log` field.

## More information and examples
{: #agent-multiline-win-moreinfo}

For more information and tutorials with example scenarios for configuring multiline processing, see the following topics.

| For information about | See |
|-----------------------|-----|
| Configuring multiline support for the Logging agent in orchestrated environments | [Topic](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-agent-multiline-new&format=markdown) |
| Multiline parsing for Java applications with Log4j | [Tutorial](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-multiline-log4j&format=markdown) |
| Multiline parsing using Helm for Java applications with Log4j | [Tutorial](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-multiline-log4j-helm&format=markdown) |
| Multiline parsing for Node.js applications using Winston | [Tutorial](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-multiline-winston&format=markdown) |
| Multiline parsing using Helm for Node.js applications using Winston | [Tutorial](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-multiline-winston-helm&format=markdown) |
{: caption="Additional resources for the Logging agent multiline processing" caption-side="bottom"}