> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/ja/ptaru/settings.md).

# 接続

- [サーバー設定](https://docs.radiusaas.com/ja/ptaru/settings/settings-server.md): サーバー設定は https://YOURNAME.radius-as-a-service.com/settings/server で確認できます
- [信頼済み証明書](https://docs.radiusaas.com/ja/ptaru/settings/trusted-roots.md)
- [プロキシ設定](https://docs.radiusaas.com/ja/ptaru/settings/settings-proxy.md): プロキシ設定は https://YOURNAME.radius-as-a-service.com/settings/proxy で確認できます
- [SCEPman 接続](https://docs.radiusaas.com/ja/ptaru/settings/scepman-jie-xu.md)
- [ログエクスポーター](https://docs.radiusaas.com/ja/ptaru/settings/log-exporter.md): ログエクスポーターを使用すると、監視とアラートのために RADIUSaaS のログを外部のセキュリティ情報およびイベント管理（SIEM）システムへ送信できます。
- [Teams](https://docs.radiusaas.com/ja/ptaru/settings/log-exporter/teams.md)
- [ログ分析](https://docs.radiusaas.com/ja/ptaru/settings/log-exporter/log-analytics.md)
- [汎用 Webhook](https://docs.radiusaas.com/ja/ptaru/settings/log-exporter/generic-webhook.md)
- [例](https://docs.radiusaas.com/ja/ptaru/settings/log-exporter/examples.md): このページでは、実際のシナリオをいくつか示し、状況に応じて Log Exporter をどのように構成するかのガイダンスを提供します。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.radiusaas.com/ja/ptaru/settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.