Squid

Docs > インテグレーション > Squid

Supported OS Linux Windows Mac OS

インテグレーションバージョン2.5.1

概要

このチェックは、Datadog Agent を通してキャッシュマネージャーから取得された Squid メトリクスを監視します。

セットアップ

インストール

Agent の Squid チェックは Datadog Agent パッケージに含まれています。Squid サーバーに追加でインストールする必要はありません。

構成

ホスト

ホストで実行中の Agent に対してこのチェックを構成するには

メトリクスの収集

Agent のコンフィギュレーションディレクトリのルートにある conf.d/ フォルダーの squid.d/conf.yaml を編集します。使用可能なすべてのコンフィギュレーションオプションの詳細については、サンプル squid.d/conf.yaml を参照してください。
Agent を再起動します。

ログ収集

Agent バージョン 6.0 以降で利用可能

Datadog Agent で、ログの収集はデフォルトで無効になっています。以下のように、datadog.yaml ファイルでこれを有効にします。
```
logs_enabled: true
```

squid.d/conf.yaml の下部にある、コンフィギュレーションブロックのコメントを解除して編集します。

logs:
  - type: file
    path: /var/log/squid/cache.log
    service: "<SERVICE-NAME>"
    source: squid
  - type: file
    path: /var/log/squid/access.log
    service: "<SERVICE-NAME>"
    source: squid

path パラメーターと service パラメーターの値を変更し、環境に合わせて構成します。

Agent を再起動します。

コンテナ化

コンテナ環境の場合は、オートディスカバリーのインテグレーションテンプレートのガイドを参照して、次のパラメーターを適用してください。

メトリクスの収集

パラメーター	値
`<INTEGRATION_NAME>`	`squid`
`<INIT_CONFIG>`	空白または `{}`
`<INSTANCE_CONFIG>`	`{"name": "<SQUID_INSTANCE_NAME>", "host": "%%host%%", "port":"3128"}`

ログ収集

Agent バージョン 6.0 以降で利用可能

Datadog Agent で、ログの収集はデフォルトで無効になっています。有効にする方法については、Kubernetes ログ収集を参照してください。

パラメーター	値
`<LOG_CONFIG>`	`{"source": "squid", "service": "<YOUR_APP_NAME>"}`

検証

Agent の status サブコマンドを実行し、Checks セクションで squid を探します。

収集データ

メトリクス

squid.cachemgr.aborted_requests (gauge)	The number of server-side HTTP requests aborted due to client-side aborts. Shown as request
squid.cachemgr.cd.kbytes_recv (gauge)	The amount of traffic received from neighbors in Cache Digest messages. Shown as kibibyte
squid.cachemgr.cd.kbytes_sent (gauge)	The amount of traffic sent to neighbors in Cache Digest messages. Shown as kibibyte
squid.cachemgr.cd.local_memory (gauge)	The amount of memory used to store Squid's own Cache Digest. Shown as kibibyte
squid.cachemgr.cd.memory (gauge)	The amount of memory used by enabling the Cache Digests' feature. Shown as kibibyte
squid.cachemgr.cd.msgs_recv (gauge)	The number of Cache Digest messages received from neighbors. Shown as message
squid.cachemgr.cd.msgs_sent (gauge)	The number of Cache Digest messages sent to neighbors. Shown as message
squid.cachemgr.cd.times_used (gauge)	The number of times Cache Digests resulted in the selection of a neighbor as the next-hop for a cache miss.
squid.cachemgr.client_http.errors (gauge)	The number of client transactions that resulted in an error. Shown as error
squid.cachemgr.client_http.hit_kbytes_out (gauge)	The amount of traffic sent to clients in responses that are cache hits Shown as kibibyte
squid.cachemgr.client_http.hits (gauge)	The number of cache hits in response to client requests. Shown as hit
squid.cachemgr.client_http.kbytes_in (gauge)	The amount of traffic received from clients in their requests. Shown as kibibyte
squid.cachemgr.client_http.kbytes_out (gauge)	The amount of traffic sent to clients in responses. Shown as kibibyte
squid.cachemgr.client_http.requests (gauge)	The number of HTTP requests received from clients Shown as request
squid.cachemgr.cpu_time (gauge)	The amount of CPU used by squid, as reported by getrusage( ). Shown as percent
squid.cachemgr.icp.kbytes_recv (gauge)	The amount of traffic received in all ICP messages, including both queries and replies. Shown as kibibyte
squid.cachemgr.icp.kbytes_sent (gauge)	The amount of traffic sent in all ICP messages, including both queries and replies. Shown as kibibyte
squid.cachemgr.icp.pkts_recv (gauge)	The number of ICP messages received from neighbors, including both queries and replies Shown as message
squid.cachemgr.icp.pkts_sent (gauge)	The number of ICP messages sent to neighbors. This includes both queries and replies but doesn't include HTCP messages. Shown as message
squid.cachemgr.icp.q_kbytes_recv (gauge)	The amount of traffic received from neighbors in ICP queries. Shown as kibibyte
squid.cachemgr.icp.q_kbytes_sent (gauge)	The amount of traffic sent to neighbors in ICP queries. Shown as kibibyte
squid.cachemgr.icp.queries_recv (gauge)	The number of ICP queries received from neighbors. Shown as query
squid.cachemgr.icp.queries_sent (gauge)	The number of ICP queries sent to neighbors. Shown as query
squid.cachemgr.icp.query_timeouts (gauge)	The number of times that Squid timed out waiting for ICP replies to arrive. Shown as error
squid.cachemgr.icp.r_kbytes_recv (gauge)	The amount of traffic received from neighbors in ICP replies. Shown as kibibyte
squid.cachemgr.icp.r_kbytes_sent (gauge)	The amount of traffic sent to neighbors in ICP replies. Shown as kibibyte
squid.cachemgr.icp.replies_queued (gauge)	The number of times Squid queued an ICP message after the initial attempt to send failed. Shown as message
squid.cachemgr.icp.replies_recv (gauge)	The number of ICP replies received from neighbors. Shown as response
squid.cachemgr.icp.replies_sent (gauge)	The number of ICP replies sent to neighbors. Shown as response
squid.cachemgr.icp.times_used (gauge)	The number of times ICP resulted in the selection of a neighbor as the next-hop for a cache miss.
squid.cachemgr.page_faults (gauge)	The number of (major) page faults as reported by getrusage( ). Shown as fault
squid.cachemgr.select_loops (gauge)	The number of times Squid called select( ) or poll( ) in the main I/O loop. Shown as item
squid.cachemgr.server.all.errors (gauge)	The number of server-side requests (all protocols) that resulted in some kind of error. Shown as error
squid.cachemgr.server.all.kbytes_in (gauge)	The amount of traffic read from the server-side for all protocols. Shown as kibibyte
squid.cachemgr.server.all.kbytes_out (gauge)	The amount of traffic written to origin servers and/or neighbor caches for server-side requests. Shown as kibibyte
squid.cachemgr.server.all.requests (gauge)	The number of requests forwarded to origin servers (or neighbor caches) for all server-side protocols. Shown as request
squid.cachemgr.server.ftp.errors (gauge)	The number of requests sent to FTP servers that resulted in an error. Shown as error
squid.cachemgr.server.ftp.kbytes_in (gauge)	The amount of traffic read from FTP servers, including control channel traffic. Shown as kibibyte
squid.cachemgr.server.ftp.kbytes_out (gauge)	The amount of traffic written to FTP servers, including control channel traffic. Shown as kibibyte
squid.cachemgr.server.ftp.requests (gauge)	The number of requests sent to FTP servers. Shown as request
squid.cachemgr.server.http.errors (gauge)	The number of server-side HTTP requests that resulted in an error. Shown as error
squid.cachemgr.server.http.kbytes_in (gauge)	The amount of traffic read from HTTP origin servers and neighbor caches. Shown as kibibyte
squid.cachemgr.server.http.kbytes_out (gauge)	The amount of traffic written to HTTP origin servers and neighbor caches. Shown as kibibyte
squid.cachemgr.server.http.requests (gauge)	The number of server-side requests to HTTP servers, including neighbor caches. Shown as request
squid.cachemgr.server.other.errors (gauge)	The number of Gopher, WAIS, and SSL requests that resulted in an error. Shown as error
squid.cachemgr.server.other.kbytes_in (gauge)	The amount of traffic read from Gopher, WAIS, and SSL servers. Shown as kibibyte
squid.cachemgr.server.other.kbytes_out (gauge)	The amount of traffic written to Gopher, WAIS, and SSL servers. Shown as kibibyte
squid.cachemgr.server.other.requests (gauge)	The number of "other" server-side requests. Currently, the other protocols are Gopher, WAIS, and SSL. Shown as request
squid.cachemgr.swap.files_cleaned (gauge)	The number of orphaned cache files removed by the periodic cleanup procedure. Shown as file
squid.cachemgr.swap.ins (gauge)	The number of objects (swap files) read from disk. Shown as file
squid.cachemgr.swap.outs (gauge)	The number of objects (swap files) saved to disk. Shown as file
squid.cachemgr.unlink.requests (gauge)	The number of unlink requests given to the (optional) unlinkd process. Shown as request

イベント

Squid チェックには、イベントは含まれません。

サービスチェック

squid.can_connect
Returns Critical if the Agent cannot connect to the Squid URL, OK otherwise.
Statuses: ok, critical

トラブルシューティング

ご不明な点は、Datadog のサポートチームまでお問合せください。