-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
MonitoringPlugin
MonitoringPlugin
is an official ASF plugin, which allows you to monitor ASF process via Prometheus time-series database.
Show
Due to technical constraints, this plugin requires generic
variant of ASF.
ASF does not come with MonitoringPlugin
bundled by default, however, it's included as optional addition in every ASF release. Download the plugin from the official release that matches your ASF version, then create a dedicated plugins/ArchiSteamFarm.OfficialPlugins.Monitoring
directory for the plugin, and finally extract the archive there.
On the next launch of ASF, the logs will indicate that the plugin has been successfully loaded through standard ASF logging mechanism. You can also verify this by navigating to /Api/metrics
URL in your IPC interface. If you are using IPC password, you'll need proper authorization, e.g. appending ?password=<YourIPCPassword>
to the /Api/metrics
URL. The content you see should look similar to below:
# TYPE asf_build_info gauge
# HELP asf_build_info Build information about ASF in form of label values
asf_build_info{variant="source",version="6.0.2.5"} 1 1713715703686
# TYPE asf_runtime_info gauge
# HELP asf_runtime_info Runtime information about ASF in form of label values
asf_runtime_info{framework=".NET 8.0.4",operating_system="Debian GNU/Linux trixie/sid",runtime="linux-x64"} 1 1713715703686
(...)
Metrics regarding ASF and the bots have dedicated prefix asf_
in their name. Other metrics e.g. regarding the .NET runtime or ASF's HttpClient
are automatically generated based on universal .NET process rules and do not carry such prefix.
Once you verified the plugin is working correctly, you can add a scrape configuration to your Prometheus instance as such:
scrape_configs:
- job_name: ArchiSteamFarm
metrics_path: /Api/metrics
params:
password:
- YourIPCPassword
static_configs:
- targets:
- 127.0.0.1:1242
Naturally, you need to ensure that your hosted Prometheus instance is able to reach ASF's IPC interface, adapt password
and targets
accordingly to your usage. If you do not have IPC password set (which is not recommended), you can skip the addition of the params
section. In case you're running multiple ASF instances with different IPC passwords, you can add additional scrape configurations, one per instance, as the query parameters can not be set on a per-target basis. Otherwise, you can declare several targets
if they share the same password.
Once your metrics are gathered by Prometheus, it's possible to use Grafana for visualization. The plugin comes with /grafana-dashboard.json
file served by standard IPC mechanisms, so assuming you're running your ASF instance with default settings, you can download it here. Alternatively, you can also grab the JSON file from our repository as well.
- π‘ Home
- π§ Configuration
- π¬ FAQ
- βοΈ Setting up (start here)
- π₯ Background games redeemer
- π’ Commands
- π οΈ Compatibility
- 𧩠ItemsMatcherPlugin
- π Management
- β±οΈ Performance
- π‘ Remote communication
- πͺ Steam Family Sharing
- π Trading
- β¨οΈ Command-line arguments
- π§ Deprecation
- π³ Docker
- π€ Extended FAQ
- π High-performance setup
- π IPC
- π Localization
- π Logging
- πΎ Low-memory setup
- π΅πΌββοΈ MonitoringPlugin
- π Plugins
- π Security
- 𧩠SteamTokenDumperPlugin
- π¦ Third-party
- π΅ Two-factor authentication