<?xml version='1.0' encoding='UTF-8'?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
<file source-language="en" target-language="pt-BR" datatype="plaintext" original="devel/plugins.md">
<trans-unit id="df3774f3" xml:space="preserve">
<target># Plugins</target>
<trans-unit id="d4691cc1" xml:space="preserve">
Custom loadable plugins extend Zabbix agent 2 functionality. They are compiled separately, but use a package shared with Zabbix agent 2.
Each plugin is a *Go* package that defines the structure and implements one or several plugin interfaces
(*Exporter*, *Configurator*, *Runner*).
- [Write your first plugin](/devel/plugins/how_to)
- [Plugin interfaces](/devel/plugins/interfaces)
- [Example plugin for Zabbix agent 2](https://git.zabbix.com/projects/AP/repos/example/browse)
Zabbix agent 2 connects bidirectionally to the plugins using UNIX sockets on Linux and Named Pipes on Windows.
The connection diagram below illustrates the communication process between Zabbix agent 2 and a loadable plugin and the metrics collection process.
</source>
<target state="needs-translation">
Os plug-ins carregáveis personalizados ampliam a funcionalidade do Zabbix Agent 2. Eles são compilados separadamente, mas usam um pacote compartilhado com o Zabbix Agent 2.
Cada plug-in é um pacote *Go* que define a estrutura e implementa uma ou várias interfaces de plug-in
(*Exporter*, *Configurator*, *Runner*).
- [Write your first plugin](/devel/plugins/how_to)
- Interfaces de plug-in](/devel/plugins/interfaces)
O Zabbix Agent 2 se conecta bidirecionalmente aos plugins usando sockets UNIX no Linux e Named Pipes no Windows.
O diagrama de conexão abaixo ilustra o processo de comunicação entre o Zabbix Agent 2 e um plug-in carregável e o processo de coleta de métricas.
</target>