Make count column available for list_stream_definition

[camillds]

What resources or data sources are affected?

From the current documentation I cannot figure out how to configure the count column for the logs pattern widget. With the following configuration it is empty:

terraform {
  required_version = ">= 1.0.0"
  required_providers {
    datadog = {
      source  = "DataDog/datadog"
      version = "~> 3.53.0"
    }
  }
}
resource "datadog_dashboard" "issue_2915" {
  title       = "issue_2915"
  description = "issue_2915"
  layout_type = "ordered"

  widget {
    list_stream_definition {
      request {
        response_format = "event_list"
        columns {
          field = "count"
          width = "auto"
        }
        columns {
          field = "volume"
          width = "auto"
        }
        columns {
          field = "service"
          width = "auto"
        }
        columns {
          field = "Message"
          width = "auto"
        }
        query {
          data_source = "logs_pattern_stream"
          query_string = "status:(error OR critical) service:$service.value env:$env.value"
        }
      }
      title = "Most Common Errors"
    }
  }
}

Feature Request

No response

References

No response

[Supam]

Hi there @camillds !

Thank you for bringing this up. This field is indeed a bit confusing to configure.
While we work to document this better you can replace the count field with matches.

The following widget configuration should create a non-empty column named "Count":

widget {
    list_stream_definition {
      request {
        response_format = "event_list"
        columns {
          field = "matches"
          width = "auto"
        }
        columns {
          field = "volume"
          width = "auto"
        }
        columns {
          field = "service"
          width = "auto"
        }
        columns {
          field = "Message"
          width = "auto"
        }
        query {
          data_source = "logs_pattern_stream"
          query_string = "status:(error OR critical) service:$service.value env:$env.value"
        }
      }
      title = "Most Common Errors"
    }
  }

[camillds]

Thanks, looks good! I have the general feeling that the nested types docs are a bit confusing and hard to navigate. Instead, some more examples like the above would be very helpful. Feel free to close this issue