# AgentApplicationService_PodLogsBatch2

PodLogsBatch returns stream of log entry in batches of upto 1000 entries for the specified pod(s).

Endpoint: GET /gitops/api/v1/agents/{agentIdentifier}/applications/{query.name}/logs/batch
Version: 1.0
Security: x-api-key

## Path parameters:

  - `agentIdentifier` (string, required)
    Agent identifier for entity.

  - `query.name` (string, required)

## Query parameters:

  - `accountIdentifier` (string)
    Account Identifier for the Entity.

  - `orgIdentifier` (string)
    Organization Identifier for the Entity.

  - `projectIdentifier` (string)
    Project Identifier for the Entity.

  - `query.namespace` (string)

  - `query.podName` (string)

  - `query.container` (string)

  - `query.sinceSeconds` (string)

  - `query.sinceTime.seconds` (string)
    Represents seconds of UTC time since Unix epoch
1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to
9999-12-31T23:59:59Z inclusive.

  - `query.sinceTime.nanos` (integer)
    Non-negative fractions of a second at nanosecond resolution. Negative
second values with fractions must still have non-negative nanos values
that count forward in time. Must be from 0 to 999,999,999
inclusive. This field may be limited in precision depending on context.

  - `query.tailLines` (string)

  - `query.follow` (boolean)

  - `query.untilTime` (string)

  - `query.filter` (string)

  - `query.kind` (string)

  - `query.group` (string)

  - `query.resourceName` (string)

  - `query.previous` (boolean)

  - `query.appNamespace` (string)

  - `query.project` (string)

## Response 200 fields (application/json):

  - `result` (object)

  - `result.entries` (array)

  - `result.entries.content` (string)

  - `result.entries.timeStamp` (object)
    Time is a wrapper around time.Time which supports correct
marshaling to YAML and JSON.  Wrappers are provided for many
of the factory methods that the time package offers.

+protobuf.options.marshal=false
+protobuf.as=Timestamp
+protobuf.options.(gogoproto.goproto_stringer)=false

  - `result.entries.timeStamp.seconds` (string)
    Represents seconds of UTC time since Unix epoch
1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to
9999-12-31T23:59:59Z inclusive.

  - `result.entries.timeStamp.nanos` (integer)
    Non-negative fractions of a second at nanosecond resolution. Negative
second values with fractions must still have non-negative nanos values
that count forward in time. Must be from 0 to 999,999,999
inclusive. This field may be limited in precision depending on context.

  - `result.entries.last` (boolean)

  - `result.entries.timeStampStr` (string)

  - `result.entries.podName` (string)

  - `result.count` (integer)

  - `result.batchIndex` (integer)

  - `error` (object)

  - `error.grpc_code` (integer)

  - `error.http_code` (integer)

  - `error.message` (string)

  - `error.http_status` (string)

  - `error.details` (array)

  - `error.details.type_url` (string)
    A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
). The name should be in a canonical form
(e.g., leading "." is not accepted).

In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme , , or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:

* If no scheme is provided,  is assumed.
* An HTTP GET on the URL must yield a [google.protobuf.Type][]
  value in binary format, or produce an error.
* Applications are allowed to cache lookup results based on the
  URL, or have them precompiled into a binary to avoid any
  lookup. Therefore, binary compatibility needs to be preserved
  on changes to types. (Use versioned type names to manage
  breaking changes.)

Note: this functionality is not currently available in the official
protobuf release, and it is not used for type URLs beginning with
type.googleapis.com. As of May 2023, there are no widely used type server
implementations and no plans to implement one.

Schemes other than ,  (or the empty scheme) might be
used with implementation specific semantics.

  - `error.details.value` (string)
    Must be a valid serialized protocol buffer of the above specified type.

## Response default fields (application/json):

  - `error` (string)

  - `code` (integer)

  - `message` (string)

  - `details` (array)

  - `details.type_url` (string)
    A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
). The name should be in a canonical form
(e.g., leading "." is not accepted).

In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme , , or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:

* If no scheme is provided,  is assumed.
* An HTTP GET on the URL must yield a [google.protobuf.Type][]
  value in binary format, or produce an error.
* Applications are allowed to cache lookup results based on the
  URL, or have them precompiled into a binary to avoid any
  lookup. Therefore, binary compatibility needs to be preserved
  on changes to types. (Use versioned type names to manage
  breaking changes.)

Note: this functionality is not currently available in the official
protobuf release, and it is not used for type URLs beginning with
type.googleapis.com. As of May 2023, there are no widely used type server
implementations and no plans to implement one.

Schemes other than ,  (or the empty scheme) might be
used with implementation specific semantics.

  - `details.value` (string)
    Must be a valid serialized protocol buffer of the above specified type.