# Agent - 22.6 (LTS)

## Agent Download

{% hint style="info" %}
To download the Agent, click [here](https://storage.googleapis.com/sym-platform/developers/rest-api/agent-22.6.5.zip).

For a list of Agent x SBE compatibilities, click [here](/admin-guide/agent-guide/sbe-x-agent-compatibility-matrix.md).
{% endhint %}

## Announcement

{% hint style="warning" %}
Since Agent 22.6, a new Release Cycle has been put in place for the Agent.

Agent 20.14 was the last agent to be released via the same schedule as SBE. Starting with the next version, Agent 22.6, agents release cadence will not be coupled to SBE's anymore, and its release version number will follow a year.month.patch pattern.

Please refer to the [main page](/admin-guide/change-log/api-agent.md) for more information (release cadence, new Long Term Support)
{% endhint %}

## Agent Changes

### Agent 22.6.5

* Fixed `/agent/actuator` endpoints so they work even if the Agent runs with same `management.server.port` than `server.port`
* Fixed security vulnerabilities.

### Agent 22.6.4

* Fixed legacy startup.sh script

### Agent 22.6.3

* Spring boot has been updated to version 2.7.2.

### Agent 22.6.2

* Fixed a bug with the authentication of the ceservice.

### Agent 22.6.1

* A parentMessageId field is now exposed in the payloads returned by the Agent when retrieving information of a message consecutive to either a reply or a forward; it can be used as a link to the original message.
* Datahose API has been released as a *Beta version for now* and until further notice. It allows any bot that is authorized by the right entitlements to retrieve all events happening on the pod, including the ones that happen in rooms it is not part of. For more information, follow the link to the [Datahose - Read Events](https://developers.symphony.com/restapi/reference/datahose-read-events) endpoint introduced in our REST API documentation.\
  \&#xNAN;*Please note that a breaking change will be introduced in the 22.7 version of the Agent: indeed the* `filters` *parameter will be removed and replaced by another one,* `eventTypes`*, which will allow to restrict the payload to the only* [*Real Time Events*](/bots/datafeed/real-time-events.md) *requested.*\
  \&#xNAN;*Note there is also a dependency on a specific Datafeed v2 version that should be soon deployed to production - more information will be available soon.*
* Consequently to the deprecation notice of the Datafeed v1 APIs on [Agent 20.14](/admin-guide/change-log/api-agent/archives/agent-20.14.md#deprecation-notice) change log, a bridge has been introduced to facilitate the transition period from Datafeed v1 APIs to Datafeed v2 service. More information are available for the [deprecation timeline and the introduction of the bridge](https://docs.developers.symphony.com/building-bots-on-symphony/datafeed) as well as the [benefits of Datafeed v2](https://developers.symphony.com/restapi/v20.14/reference/datafeed).
* Similarly to its historic capabilities on downloading messages, the ceservice is now able to download attachments even from streams it is not part of.
* Fixed a bug with Blast Message API returning unexpected 500 error message.
* Spring boot has been updated to version 2.6.8.

{% hint style="info" %}
**Important**: The logging configuration file (log4j2.xml) is now externalised and shipped within the agent zip deliverable. Inside the provided start.sh (preferred) and startup.sh (deprecated), a Java option has been added to target provided log4j2.xml : `-Dlogging.config=$LOGGING_CONFIG`. This enables you to customise the log4j2.xml content and location as needed.\
If you are using a custom start script instead of the provided ones, please make sure the new log4j2.xml file is present in the agent folder, **and add -Dlogging.config=log4j2.xml to the Java command line in your script**, for the logs to be generated at the location specified in `-Dlogs.directory`, according to the rules defined in log4j2.xml.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.developers.symphony.com/admin-guide/change-log/api-agent/archives/agent-22.6-lts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.