Merge branch 'master' into telegraf-templates

pull/6375/head
Jason Stirnaman 2025-09-16 08:59:58 -05:00 committed by GitHub
commit c44fa799ce
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
23 changed files with 591 additions and 138 deletions

View File

@ -2,7 +2,7 @@ version: 2.1
jobs:
build:
docker:
- image: cimg/node:20.12.1
- image: cimg/node:24.5.0
environment:
S3DEPLOY_VERSION: "2.11.0"
# From https://github.com/bep/s3deploy/releases

View File

@ -48,23 +48,35 @@ Descriptions should follow consistent patterns:
## Hugo shortcodes in Markdown
- `{{% code-placeholders "PLACEHOLDER1|PLACEHOLDER2" %}}`: Use this shortcode to define placeholders in code snippets.
- `{{% /code-placeholders %}}`: End the shortcode.
- `{{% code-placeholder-key %}}`: Use this shortcode to define a specific placeholder key.
- `{{% /code-placeholder-key %}}`: End the specific placeholder key shortcode.
**Syntax**:
- Use the `placeholders` code block attribute to define placeholder patterns:
```<language> { placeholders="<expr>" }
function sampleCode () {};
```
**Old (deprecated) syntax**:
- `{{% code-placeholders "PLACEHOLDER1|PLACEHOLDER2" %}}`
- `{{% /code-placeholders %}}`
**Define a placeholder key (typically following the example)**:
- `{{% code-placeholder-key %}}`: Use this shortcode to define a placeholder key
- `{{% /code-placeholder-key %}}`: Use this shortcode to close the key name
- Follow with a description
## Language-Specific Placeholder Formatting
- **Bash/Shell**: Use uppercase variables with no quotes or prefix
```bash
```bash { placeholders="DATABASE_NAME" }
--database DATABASE_NAME
```
- Python: Use string literals with quotes
```python
```python { placeholders="DATABASE_NAME" }
database_name='DATABASE_NAME'
```
- JSON: Use key-value pairs with quotes
```json
```json { placeholders="DATABASE_NAME" }
{
"database": "DATABASE_NAME"
}
@ -75,8 +87,7 @@ Descriptions should follow consistent patterns:
### InfluxDB CLI Commands
This pattern appears frequently in CLI documentation:
{{% code-placeholders "DATABASE_NAME|AUTH_TOKEN" %}}
```bash
```bash { placeholders="DATABASE_NAME|AUTH_TOKEN" }
influxdb3 write \
--database DATABASE_NAME \
--token AUTH_TOKEN \

View File

@ -0,0 +1,55 @@
## InfluxDB v1 Release Documentation
**Release Version:** v1.x.x
**Release Type:** [ ] OSS [ ] Enterprise [ ] Both
### Description
Brief description of the release and documentation changes.
### Release Documentation Checklist
#### Release Notes
- [ ] Generate release notes from changelog
- [ ] OSS: Use commit messages from GitHub release tag `https://github.com/influxdata/influxdb/releases/tag/v1.x.x`
- [ ] Enterprise: Use `https://dl.influxdata.com/enterprise/nightlies/master/CHANGELOG.md`
- [ ] **Note**: For Enterprise releases, include important updates, features, and fixes from the corresponding OSS tag
- [ ] Update release notes in appropriate location
- [ ] OSS: `/content/influxdb/v1/about_the_project/releasenotes-changelog.md`
- [ ] Enterprise: `/content/enterprise_influxdb/v1/about-the-project/release-notes.md`
- [ ] Ensure release notes follow documentation formatting standards
#### Version Updates
- [ ] Update patch version in `/data/products.yml`
- [ ] OSS: `influxdb > v1 > latest`
- [ ] Enterprise: `enterprise_influxdb > v1 > latest`
- [ ] Update version references in documentation
- [ ] Installation guides
- [ ] Docker documentation
- [ ] Download links
- [ ] Code examples with version-specific commands
#### Content Verification
- [ ] Review breaking changes and update migration guides if needed
- [ ] Update compatibility matrices if applicable
- [ ] Verify all download links work correctly
- [ ] Check that version-specific features are documented
#### Testing
- [ ] Build documentation locally and verify changes render correctly
- [ ] Test all updated links
- [ ] Run link validation: `yarn test:links content/influxdb/v1/**/*.md`
- [ ] Run link validation: `yarn test:links content/enterprise_influxdb/v1/**/*.md`
### Related Resources
- DAR Issue: #
- OSS Release: https://github.com/influxdata/influxdb/releases/tag/v1.x.x
- Enterprise Changelog: https://dl.influxdata.com/enterprise/nightlies/master/CHANGELOG.md
- Slack Discussion: [Link to #releases thread]
### Post-Merge Actions
- [ ] Verify documentation is deployed to production
- [ ] Announce in #docs channel
- [ ] Close related DAR issue(s)
---
**Note:** For Enterprise releases, ensure you have access to the Enterprise changelog and coordinate with the release team for timing.

View File

@ -95,7 +95,7 @@ jobs:
curl -L -H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}" \
-o link-checker-info.json \
"https://api.github.com/repos/influxdata/docs-v2/releases/tags/link-checker-v1.2.3"
"https://api.github.com/repos/influxdata/docs-v2/releases/tags/link-checker-v1.2.4"
# Extract download URL for linux binary
DOWNLOAD_URL=$(jq -r '.assets[] | select(.name | test("link-checker.*linux")) | .url' link-checker-info.json)

View File

@ -11,12 +11,9 @@ alt_links:
v1: /influxdb/v1/about_the_project/release-notes/
---
## v1.12.x {date="TBD"}
<span id="v1.12.x"></span>
> [!Important]
> #### Pre-release documentation
>
> This release is not yet available. [**v{{% latest-patch %}}**](#v1118) is the latest InfluxDB Enterprise v1 release.
## v1.12.2 {date="2025-09-15"}
> [!Important]
> #### Upgrade meta nodes first
@ -24,61 +21,40 @@ alt_links:
> When upgrading to InfluxDB Enterprise 1.12.1+, upgrade meta nodes before
> upgrading data nodes.
## Features
### Features
- Add additional log output when using
[`influx_inspect buildtsi`](/enterprise_influxdb/v1/tools/influx_inspect/#buildtsi) to
rebuild the TSI index.
<!-- TODO: Uncomment with 1.12.x release:
- Use [`influx_inspect export`](/enterprise_influxdb/v1/tools/influx_inspect/#export) with
[`-tsmfile` option](/enterprise_influxdb/v1/tools/influx_inspect/#--tsmfile-tsm_file-) to
export a single TSM file.
-->
<!-- TODO: Remove with 1.12.x release: -->
- Use [`influx_inspect export`](/enterprise_influxdb/v1/tools/influx_inspect/#export) with
`-tsmfile` option to
export a single TSM file.
- Add `-m` flag to the [`influxd-ctl show-shards` command](/enterprise_influxdb/v1/tools/influxd-ctl/show-shards/)
to output inconsistent shards.
- Allow the specification of a write window for retention policies.
- Add `fluxQueryRespBytes` metric to the `/debug/vars` metrics endpoint.
- Log whenever meta gossip times exceed expiration.
<!-- TODO: Uncomment with 1.12.x release:
- Add [`query-log-path` configuration option](/enterprise_influxdb/v1/administration/configure/config-data-nodes/#query-log-path)
to data nodes.
- Add [`aggressive-points-per-block` configuration option](/influxdb/v1/administration/config/#aggressive-points-per-block)
to prevent TSM files from not getting fully compacted.
-->
<!-- TODO: Remove with 1.12.x release: -->
- Add `query-log-path` configuration option to data nodes.
- Add `aggressive-points-per-block` configuration option to prevent TSM files from not getting fully compacted.
- Log TLS configuration settings on startup.
- Check for TLS certificate and private key permissions.
- Add a warning if the TLS certificate is expired.
- Add authentication to the Raft portal and add the following related _data_
node configuration options:
<!-- Uncomment with 1.12.x release
- [`[meta].raft-portal-auth-required`](/enterprise_influxdb/v1/administration/configure/config-data-nodes/#raft-portal-auth-required)
- [`[meta].raft-dialer-auth-required`](/enterprise_influxdb/v1/administration/configure/config-data-nodes/#raft-dialer-auth-required)
-->
<!-- TODO: Remove with 1.12.x release: -->
- `[meta].raft-portal-auth-required`
- `[meta].raft-dialer-auth-required`
- Improve error handling.
- InfluxQL updates:
- Delete series by retention policy.
<!-- TODO: Uncomment with 1.12.x release:
- Allow retention policies to discard writes that fall within their range, but
outside of [`FUTURE LIMIT`](/enterprise_influxdb/v1/query_language/manage-database/#future-limit)
and [`PAST LIMIT`](/enterprise_influxdb/v1/query_language/manage-database/#past-limit).
-->
<!-- TODO: Remove with 1.12.x release: -->
- Allow retention policies to discard writes that fall within their range, but
outside of `FUTURE LIMIT` and `PAST LIMIT`.
## Bug fixes
### Bug fixes
- Fixed SSH key usage for cloning PCL/HT.
- Log rejected writes to subscriptions.
- Update `xxhash` and avoid `stringtoslicebyte` in the cache.
- Prevent a panic when a shard group has no shards.
@ -89,7 +65,7 @@ alt_links:
- Update the `/shard-status` API to return the correct result and use a
consistent "idleness" definition for shards.
## Other
### Other
- Update Go to 1.23.5.
- Upgrade Flux to v0.196.1.
@ -230,26 +206,24 @@ alt_links:
## v1.11.3 {date="2023-10-12"}
{{% warn %}}
#### Series file compaction on startup
With InfluxDB Enterprise v1.11.3, on startup, InfluxDB runs the
`influxd_inspect -compact-series-file` command to [compact series files](/enterprise_influxdb/v1/tools/influx_inspect/#--compact-series-file-) before data nodes are started.
Series files are stored in `_series` directories inside the
[InfluxDB data directory](/enterprise_influxdb/v1/concepts/file-system-layout/#data-node-file-system-layout). Default: `/var/lib/data/<db-name>/_series`
- InfluxDB Enterprise v1.11.4+ introduces a configuration setting to optionally
compact series on startup.
- If any series files are corrupt, the `influx_inspect` or `influxd` processes on
the data node may fail to start. In both cases, delete the series file
directories before restarting the database. InfluxDB will automatically
regenerate the deleted series files when the database is restarted.
- To check if series files are corrupt before starting the database, run the
[`influx_inspect verify-seriesfile` command](/enterprise_influxdb/v1/tools/influx_inspect/#verify-seriesfile)
while the database is off-line.
- If series files are large (20+ gigabytes), it may also be faster to delete the
series file directories before starting the database.
{{% /warn %}}
> [!Important]
> #### Series file compaction on startup
>
> With InfluxDB Enterprise v1.11.3, on startup, InfluxDB runs the
> `influxd_inspect -compact-series-file` command to [compact series files](/enterprise_influxdb/v1/tools/influx_inspect/#--compact-series-file-) before data nodes are started.
> Series files are stored in `_series` directories inside the
> [InfluxDB data directory](/enterprise_influxdb/v1/concepts/file-system-layout/#data-node-file-system-layout). Default: `/var/lib/data/<db-name>/_series`
>
> - InfluxDB Enterprise v1.11.4+ introduces a configuration setting to optionally
> compact series on startup.
> - If any series files are corrupt, the `influx_inspect` or `influxd` processes on
> the data node may fail to start. In both cases, delete the series file directories and [rebuild the indexes](/enterprise_influxdb/v1/administration/upgrading/#rebuild-tsi-indexes) before restarting the database. InfluxDB automatically
> regenerates the deleted series files when the database restarts.
> - To check if series files are corrupt before starting the database, run the
> [`influx_inspect verify-seriesfile` command](/enterprise_influxdb/v1/tools/influx_inspect/#verify-seriesfile)
> while the database is off-line.
> - If series files are large (20+ gigabytes), it may be faster to delete the
> series file directories before starting the database.
### Bug Fixes
@ -1181,7 +1155,8 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1/about_the_project/relea
## v1.5.0 {date="2018-03-06"}
> ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release
> [!Note]
> This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release
> notes](/influxdb/v1/about_the_project/release-notes/) for more information about the InfluxDB OSS release.
For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1/about_the_project/whats_new/).

View File

@ -1679,9 +1679,10 @@ max-version = "tls1.3"
Default is `"tls1.3"`.
Minimum version of the TLS protocol that will be negotiated.
Valid values include: `tls1.0`, `tls1.1`, and `tls1.3`.
Valid values include: `tls1.0`, `tls1.1`, `tls1.2`, and `tls1.3`.
If not specified, `min-version` is the minimum TLS version specified in the [Go `crypto/tls` package](https://golang.org/pkg/crypto/tls/#pkg-constants).
In this example, `tls1.3` specifies the minimum version as TLS 1.3.
In the preceding example, `min-version = "tls1.3"` specifies the minimum version as TLS 1.3.
Environment variable: `INFLUXDB_TLS_MIN_VERSION`
@ -1690,9 +1691,10 @@ Environment variable: `INFLUXDB_TLS_MIN_VERSION`
Default is `"tls1.3"`.
The maximum version of the TLS protocol that will be negotiated.
Valid values include: `tls1.0`, `tls1.1`, and `tls1.3`.
Valid values include: `tls1.0`, `tls1.1`, `tls1.2`, and `tls1.3`.
If not specified, `max-version` is the maximum TLS version specified in the [Go `crypto/tls` package](https://golang.org/pkg/crypto/tls/#pkg-constants).
In this example, `tls1.3` specifies the maximum version as TLS 1.3.
In the preceding example, `max-version = "tls1.3"` specifies the maximum version as TLS 1.3.
Environment variable: `INFLUXDB_TLS_MAX_VERSION`

View File

@ -13,49 +13,28 @@ alt_links:
enterprise_v1: /enterprise_influxdb/v1/about-the-project/release-notes/
---
## v1.12.x {date="TBD"}
> [!Important]
> #### Pre-release documentation
>
> This release is not yet available. [**v{{% latest-patch %}}**](#v1118) is the latest InfluxDB v1 release.
## v1.12.2 {date="2025-09-15"}
## Features
### Features
- Add additional log output when using
[`influx_inspect buildtsi`](/influxdb/v1/tools/influx_inspect/#buildtsi) to
rebuild the TSI index.
<!-- TODO: Uncomment with 1.12.x release:
- Use [`influx_inspect export`](/influxdb/v1/tools/influx_inspect/#export) with
[`-tsmfile` option](/influxdb/v1/tools/influx_inspect/#--tsmfile-tsm_file-) to
export a single TSM file.
-->
<!-- TODO: Remove with 1.12.x release: -->
- Use [`influx_inspect export`](/influxdb/v1/tools/influx_inspect/#export) with
`-tsmfile` option to
export a single TSM file.
- Add `fluxQueryRespBytes` metric to the `/debug/vars` metrics endpoint.
<!-- TODO: Uncomment with 1.12.x release:
- Add [`aggressive-points-per-block` configuration option](/influxdb/v1/administration/config/#aggressive-points-per-block)
to prevent TSM files from not getting fully compacted.
-->
<!-- TODO: Remove with 1.12.x release: -->
- Add `aggressive-points-per-block` configuration option
to prevent TSM files from not getting fully compacted.
- Improve error handling.
- InfluxQL updates:
- Delete series by retention policy.
<!-- TODO: Uncomment with 1.12.x release:
- Allow retention policies to discard writes that fall within their range, but
outside of [`FUTURE LIMIT`](/influxdb/v1/query_language/manage-database/#future-limit)
and [`PAST LIMIT`](/influxdb/v1/query_language/manage-database/#past-limit).
-->
<!-- TODO: Remove with 1.12.x release: -->
- Allow retention policies to discard writes that fall within their range, but
outside of `FUTURE LIMIT` and `PAST LIMIT`.
## Bug fixes
### Bug fixes
- Log rejected writes to subscriptions.
- Update `xxhash` and avoid `stringtoslicebyte` in the cache.
@ -65,7 +44,7 @@ alt_links:
- Ensure temporary files are removed after failed compactions.
- Do not panic on invalid multiple subqueries.
## Other
### Other
- Update Go to 1.23.5.
- Upgrade Flux to v0.196.1.

View File

@ -16,13 +16,13 @@ aliases:
- /influxdb3/clustered/install/licensing/
---
Install your InfluxDB Clustered license in your cluster to authorize the use
of the InfluxDB Clustered software.
Install your {{% product-name %}} license in your cluster to authorize the use
of the {{% product-name %}} software.
## Install your InfluxDB license
## Install your {{% product-name %}} license
1. If you haven't already,
[request an InfluxDB Clustered license](https://influxdata.com/contact-sales).
[request an {{% product-name %}} license](https://influxdata.com/contact-sales).
2. InfluxData provides you with a `license.yml` file that encapsulates your
license token as a custom Kubernetes resource.
3. Use `kubectl` to apply and create the `License` resource in your InfluxDB
@ -34,28 +34,28 @@ of the InfluxDB Clustered software.
kubectl apply --filename license.yml --namespace influxdb
```
InfluxDB Clustered detects the `License` resource and extracts the credentials
into a secret required by InfluxDB Clustered Kubernetes pods.
{{% product-name %}} detects the `License` resource and extracts the credentials
into a secret required by {{% product-name %}} Kubernetes pods.
Pods validate the license secret both at startup and periodically (roughly once
per hour) while running.
## Upgrade from a non-licensed release
If you are currently using a non-licensed preview release of InfluxDB Clustered
If you are currently using a non-licensed preview release of {{% product-name %}}
and want to upgrade to a licensed release, do the following:
1. [Install an InfluxDB license](#install-your-influxdb-license)
1. [Install an {{% product-name %}} license](#install-your-influxdb-clustered-license)
2. If you [use the `AppInstance` resource configuration](/influxdb3/clustered/install/set-up-cluster/configure-cluster/directly/)
to configure your cluster, in your `myinfluxdb.yml`, update the package
version defined in `spec.package.image` to use a licensed release.
If using the InfluxDB Clustered Helm chart, update the `image.tag` property
If using the {{% product-name %}} Helm chart, update the `image.tag` property
in your `values.yaml`to use a licensed release.
> [!Warning]
> #### Upgrade to checkpoint releases first
>
> When upgrading InfluxDB Clustered, always upgrade to each
> When upgrading {{% product-name %}}, always upgrade to each
> [checkpoint release](/influxdb3/clustered/admin/upgrade/#checkpoint-releases)
> first, before proceeding to newer versions.
> Upgrading past a checkpoint release without first upgrading to it may result in
@ -103,6 +103,33 @@ the version number to upgrade to.
After you have activated your license, use the following signals to verify the
license is active and functioning.
In your commands, replace the following:
- {{% code-placeholder-key %}}`NAMESPACE`{{% /code-placeholder-key %}}:
your [InfluxDB namespace](/influxdb3/clustered/install/set-up-cluster/configure-cluster/#create-a-namespace-for-influxdb)
- {{% code-placeholder-key %}}`POD_NAME`{{% /code-placeholder-key %}}:
your [InfluxDB Kubernetes pod](/influxdb3/clustered/install/set-up-cluster/deploy/#inspect-cluster-pods)
### Verify database components
After you [install your license](#install-your-influxdb-clustered-license),
run the following command to check that database pods start up and are in the
`Running` state:
<!--pytest.mark.skip-->
```bash
kubectl get pods -l app=iox --namespace influxdb
```
If a `Pod` fails to start, run the following command to view pod information:
<!--pytest.mark.skip-->
```sh { placeholders="POD_NAME" }
kubectl describe pod POD_NAME --namespace influxdb
```
### Verify the `Secret` exists
Run the following command to verify that the licensing activation created a
@ -116,7 +143,8 @@ kubectl get secret iox-license --namespace influxdb
If the secret doesn't exist,
[view `license-controller` logs](#view-license-controller-logs) for more
information or errors.
information or errors. For troubleshooting guidance, see
[Manage your {{% product-name %}} license](/influxdb3/clustered/admin/licensing/).
### View `license controller` logs
@ -130,7 +158,20 @@ following command:
kubectl logs deployment/license-controller --namespace influxdb
```
For more information about InfluxDB Clustered licensing, see
[Manage your InfluxDB Clustered license](/influxdb3/clustered/admin/licensing/)
## Renew your license
> [!Tip]
> Before your license expires, your InfluxData sales representative will
> contact you about license renewal.
> You may also contact your sales representative at any time.
If you have an expired license, follow the same process to [install your renewed license](#install-your-influxdb-clustered-license) using the new `license.yml` file provided by InfluxData.
> [!Important]
> #### Recover from an expired license
> If your license has already expired and your cluster pods are in a `CrashLoopBackoff` state, applying a valid renewed license will restore normal operation. For more information about license enforcement and recovery, see [Manage your {{% product-name %}} license](/influxdb3/clustered/admin/licensing/).
For more information about {{% product-name %}} licensing, including license enforcement, grace periods, and detailed troubleshooting, see
[Manage your {{% product-name %}} license](/influxdb3/clustered/admin/licensing/).
{{< page-nav prev="/influxdb3/clustered/install/set-up-cluster/configure-cluster/" prevText="Configure your cluster" next="/influxdb3/clustered/install/set-up-cluster/deploy/" nextText="Deploy your cluster" keepTab=true >}}

View File

@ -0,0 +1,15 @@
---
title: influxdb3 install
description: >
The `influxdb3 install` command and its subcommands manage package installations for the InfluxDB 3 processing engine.
menu:
influxdb3_core:
parent: influxdb3
name: influxdb3 install
weight: 300
source: /shared/influxdb3-cli/install/_index.md
---
<!--
//SOURCE - content/shared/influxdb3-cli/install/_index.md
-->

View File

@ -0,0 +1,19 @@
---
title: influxdb3 install package
description: >
The `influxdb3 install package` command installs Python packages for use in InfluxDB 3 processing engine plugins.
influxdb3/core/tags: [cli, processing engine, plugins]
menu:
influxdb3_core:
name: influxdb3 install package
parent: influxdb3 install
weight: 201
related:
- /influxdb3/core/process/
- /influxdb3/core/plugins/
source: /shared/influxdb3-cli/install/package.md
---
<!--
//SOURCE - content/shared/influxdb3-cli/install/package.md
-->

View File

@ -0,0 +1,15 @@
---
title: influxdb3 install
description: >
The `influxdb3 install` command and its subcommands manage package installations for the InfluxDB 3 processing engine.
menu:
influxdb3_enterprise:
parent: influxdb3
name: influxdb3 install
weight: 300
source: /shared/influxdb3-cli/install/_index.md
---
<!--
//SOURCE - content/shared/influxdb3-cli/install/_index.md
-->

View File

@ -0,0 +1,19 @@
---
title: influxdb3 install package
description: >
The `influxdb3 install package` command installs Python packages for use in InfluxDB 3 processing engine plugins.
influxdb3/enterprise/tags: [cli, processing engine, plugins]
menu:
influxdb3_enterprise:
name: influxdb3 install package
parent: influxdb3 install
weight: 201
related:
- /influxdb3/enterprise/process/
- /influxdb3/enterprise/plugins/
source: /shared/influxdb3-cli/install/package.md
---
<!--
//SOURCE - content/shared/influxdb3-cli/install/package.md
-->

View File

@ -47,6 +47,7 @@ influxdb3 serve
{{% show-in "enterprise" %}} - [node-id-from-env](#node-id-from-env){{% /show-in %}}
- [object-store](#object-store)
{{% show-in "enterprise" %}}
- [num-cores](#num-cores)
- [num-database-limit](#num-database-limit)
- [num-table-limit](#num-table-limit)
- [num-total-columns-per-table-limit](#num-total-columns-per-table-limit)
@ -297,6 +298,23 @@ This option supports the following values:
{{% show-in "enterprise" %}}
---
#### num-cores
Limits the total number of CPU cores that can be used by the server.
Default is determined by your {{% product-name %}} license:
- **Trial**: up to 256 cores
- **At-Home**: 2 cores
- **Commercial**: per contract
| influxdb3 serve option | Environment variable |
| :--------------------- | :--------------------------------- |
| `--num-cores` | `INFLUXDB3_ENTERPRISE_NUM_CORES` |
For more information about licensing, see [Manage license](/influxdb3/enterprise/admin/license).
---
#### num-database-limit
Limits the total number of active databases.
@ -1380,9 +1398,11 @@ Determines whether WAL replay should fail when encountering errors.
#### wal-replay-concurrency-limit
Sets the maximum number of concurrent WAL replay operations.
Concurrency limit during WAL replay.
Setting this number too high can lead to OOM.
The default is dynamically determined.
**Default:** `16`
**Default:** `max(num_cpus, 10)`
| influxdb3 serve option | Environment variable |
| :--------------------------------- | :------------------------------------------ |
@ -1891,9 +1911,10 @@ Specifies how far back to look when creating generation 1 Parquet files.
#### retention-check-interval
Defines how often the system checks for data that should be deleted according to retention policies.
The interval at which retention policies are checked and enforced.
Enter as a human-readable time--for example: `30m` or `1h`.
**Default:** `1h`
**Default:** `30m`
| influxdb3 serve option | Environment variable |
| :----------------------------- | :--------------------------------------- |

View File

@ -32,6 +32,7 @@ influxdb3 create trigger [OPTIONS] \
| | `--disabled` | Create the trigger in disabled state |
| | `--error-behavior` | Error handling behavior: `log`, `retry`, or `disable` |
| | `--run-asynchronous` | Run the trigger asynchronously, allowing multiple triggers to run simultaneously (default is synchronous) |
{{% show-in "enterprise" %}}| | `--node-spec` | Which node(s) the trigger should be configured on. Two value formats are supported: `all` (default) - applies to all nodes, or `nodes:<node-id>[,<node-id>..]` - applies only to specified comma-separated list of nodes |{{% /show-in %}}
| | `--tls-ca` | Path to a custom TLS certificate authority (for testing or self-signed certificates) |
| `-h` | `--help` | Print help information |
| | `--help-all` | Print detailed help information |

View File

@ -0,0 +1,5 @@
The `influxdb3 install` command includes the following subcommands:
| Subcommand | Description |
|:----------|:------------|
| [`package`](/influxdb3/version/reference/cli/influxdb3/install/package/) | Install Python packages for processing engine plugins |

View File

@ -0,0 +1,54 @@
The `influxdb3 install package` command installs Python packages for use in [InfluxDB 3 processing engine plugins](/influxdb3/version/process/).
## Usage
```bash { placeholders="PACKAGE_NAME" }
influxdb3 install package --packages PACKAGE_NAME
```
Replace the following:
- {{% code-placeholder-key %}}`PACKAGE_NAME`{{% /code-placeholder-key %}}: the name of the Python package to install
## Options
| Option | Description | Default | Environment | Required |
|--------|-------------|---------|-------------|----------|
| `--packages` | Python package names to install (comma-separated) | | | |
| `-r`, `--requirements` | Path to requirements.txt file | | | |
| `-H`, `--host` | Host URL of the running {{< product-name >}} server | `http://127.0.0.1:8181` | `INFLUXDB3_HOST_URL` | |
| `--token` | The token for authentication with the InfluxDB 3 server | | `INFLUXDB3_AUTH_TOKEN` | |
| `--tls-ca` | Path to a custom TLS certificate authority for testing with self-signed certificates | | `INFLUXDB3_TLS_CA` | |
| `--plugin-dir` | Location of the plugins directory | | `INFLUXDB3_PLUGIN_DIR` | |
| `--virtual-env-location` | Location of the Python virtual environment | | `VIRTUAL_ENV` | |
| `--package-manager` | Package manager to use for installing packages | `discover` | | |
## Examples
### Install a single package
```bash { placeholders="pandas" }
influxdb3 install package --packages pandas
```
### Install multiple packages
```bash
influxdb3 install package --packages pandas,numpy,scipy
```
### Install packages from requirements file
```bash
influxdb3 install package -r requirements.txt
```
### Install with authentication
```bash { placeholders="AUTH_TOKEN|pandas" }
influxdb3 install package --token AUTH_TOKEN --packages pandas
```
Replace the following:
- {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}: your {{% token-link "admin" %}} for your {{< product-name >}} instance

View File

@ -96,6 +96,91 @@ less than or equal to `08-19-2019T13:00:00Z`.
{{% /expand %}}
{{< /expand-wrapper >}}
### Filter data by dynamic date ranges
Use date and time functions to filter data by relative time periods that automatically update.
#### Get data from yesterday
```sql
SELECT *
FROM h2o_feet
WHERE "location" = 'santa_monica'
AND time >= DATE_TRUNC('day', NOW() - INTERVAL '1 day')
AND time < DATE_TRUNC('day', NOW())
```
{{< expand-wrapper >}}
{{% expand "View example results" %}}
This query filters data to include only records from the previous calendar day:
- `NOW() - INTERVAL '1 day'` calculates yesterday's timestamp
- `DATE_TRUNC('day', ...)` truncates to the start of that day (00:00:00)
- The range spans from yesterday at 00:00:00 to today at 00:00:00
| level description | location | time | water_level |
| :---------------- | :----------- | :----------------------- | :---------- |
| below 3 feet | santa_monica | 2019-08-18T12:00:00.000Z | 2.533 |
| below 3 feet | santa_monica | 2019-08-18T12:06:00.000Z | 2.543 |
| below 3 feet | santa_monica | 2019-08-18T12:12:00.000Z | 2.385 |
| below 3 feet | santa_monica | 2019-08-18T12:18:00.000Z | 2.362 |
| below 3 feet | santa_monica | 2019-08-18T12:24:00.000Z | 2.405 |
| below 3 feet | santa_monica | 2019-08-18T12:30:00.000Z | 2.398 |
{{% /expand %}}
{{< /expand-wrapper >}}
#### Get data from the last 24 hours
```sql
SELECT *
FROM h2o_feet
WHERE time >= NOW() - INTERVAL '1 day' AND location = 'santa_monica'
```
{{< expand-wrapper >}}
{{% expand "View example results" %}}
This query returns data from exactly 24 hours before the current time. Unlike the "yesterday" example, this creates a rolling 24-hour window that moves with the current time.
| level description | location | time | water_level |
| :---------------- | :----------- | :----------------------- | :---------- |
| below 3 feet | santa_monica | 2019-08-18T18:00:00.000Z | 2.120 |
| below 3 feet | santa_monica | 2019-08-18T18:06:00.000Z | 2.028 |
| below 3 feet | santa_monica | 2019-08-18T18:12:00.000Z | 1.982 |
| below 3 feet | santa_monica | 2019-08-19T06:00:00.000Z | 1.825 |
| below 3 feet | santa_monica | 2019-08-19T06:06:00.000Z | 1.753 |
| below 3 feet | santa_monica | 2019-08-19T06:12:00.000Z | 1.691 |
{{% /expand %}}
{{< /expand-wrapper >}}
#### Get data from the current week
```sql
SELECT *
FROM h2o_feet
WHERE time >= DATE_TRUNC('week', NOW()) AND location = 'santa_monica'
```
{{< expand-wrapper >}}
{{% expand "View example results" %}}
This query returns all data from the start of the current week (Monday at 00:00:00) to the current time. The DATE_TRUNC('week', NOW()) function truncates the current timestamp to the beginning of the week.
| level description | location | time | water_level |
| :---------------- | :----------- | :----------------------- | :---------- |
| below 3 feet | santa_monica | 2019-08-12T00:00:00.000Z | 2.064 |
| below 3 feet | santa_monica | 2019-08-14T09:30:00.000Z | 2.116 |
| below 3 feet | santa_monica | 2019-08-16T15:45:00.000Z | 1.952 |
| below 3 feet | santa_monica | 2019-08-18T12:00:00.000Z | 2.533 |
| below 3 feet | santa_monica | 2019-08-18T18:00:00.000Z | 2.385 |
| below 3 feet | santa_monica | 2019-08-19T10:30:00.000Z | 1.691 |
{{% /expand %}}
{{< /expand-wrapper >}}
### Filter data using the OR operator
```sql

View File

@ -5,6 +5,46 @@
> All updates to Core are automatically included in Enterprise.
> The Enterprise sections below only list updates exclusive to Enterprise.
## v3.4.2 {date="2025-09-11"}
### Core
#### Features
- No new features in this release
#### Bug fixes
- **Database reliability**:
- TableIndexCache initialization and ObjectStore improvements
- Persister doesn't need a TableIndexCache
#### HTTP API changes
- **v2 write API**: Standardized `/api/v2/write` error response format to match other InfluxDB editions. Error responses now use the consistent format: `{"code": "<code>", "message": "<detailed message>"}` ([#26787](https://github.com/influxdata/influxdb/pull/26787))
### Enterprise
All Core updates are included in Enterprise. Additional Enterprise-specific features and fixes:
#### Features
- **Storage engine**: Pass in root CA and disable TLS verify for object store
- **Support**: Add support for manually stopping a node
#### Bug fixes
- **Bug fix**: Generation detail path calculation panic
- **Database reliability**: Pass TableIndexCache through to PersistedFiles
#### Operational improvements
- **Compaction optimizations**:
- Compaction cleaner now waits for 1 hour by default (previously 10 minutes)
- Compaction producer now waits for 10 seconds before starting compaction cycle
- **Catalog synchronization**: Background catalog update is synchronized every 1 second (previously 10 seconds)
- **Logging improvements**: Added clear logging to indicate what sequence is persisted on producer side and what is consumed by the consumer side
## v3.4.1 {date="2025-08-28"}
### Core

View File

@ -11,6 +11,84 @@ menu:
weight: 60
---
## v1.36.0 {date="2025-09-08"}
### Important Changes
- Pull request [#17355](https://github.com/influxdata/telegraf/pull/17355) updates `profiles` support in `inputs.opentelemetry` from v1 experimental to v1 development, following upstream changes to the experimental API. This update modifies metric output. For example, the `frame_type`, `stack_trace_id`, `build_id`, and `build_id_type` fields are no longer reported. The value format of other fields or tags might also have changed. For more information, see the [OpenTelemetry documentation](https://opentelemetry.io/docs/).
### New Plugins
- [#17368](https://github.com/influxdata/telegraf/pull/17368) `inputs.turbostat` Add plugin
- [#17078](https://github.com/influxdata/telegraf/pull/17078) `processors.round` Add plugin
### Features
- [#16705](https://github.com/influxdata/telegraf/pull/16705) `agent` Introduce labels and selectors to enable and disable plugins
- [#17547](https://github.com/influxdata/telegraf/pull/17547) `inputs.influxdb_v2_listener` Add `/health` route
- [#17312](https://github.com/influxdata/telegraf/pull/17312) `inputs.internal` Allow to collect statistics per plugin instance
- [#17024](https://github.com/influxdata/telegraf/pull/17024) `inputs.lvm` Add sync_percent for lvm_logical_vol
- [#17355](https://github.com/influxdata/telegraf/pull/17355) `inputs.opentelemetry` Upgrade otlp proto module
- [#17156](https://github.com/influxdata/telegraf/pull/17156) `inputs.syslog` Add support for RFC3164 over TCP
- [#17543](https://github.com/influxdata/telegraf/pull/17543) `inputs.syslog` Allow limiting message size in octet counting mode
- [#17539](https://github.com/influxdata/telegraf/pull/17539) `inputs.x509_cert` Add support for Windows certificate stores
- [#17244](https://github.com/influxdata/telegraf/pull/17244) `output.nats` Allow disabling stream creation for externally managed streams
- [#17474](https://github.com/influxdata/telegraf/pull/17474) `outputs.elasticsearch` Support array headers and preserve commas in values
- [#17548](https://github.com/influxdata/telegraf/pull/17548) `outputs.influxdb` Add internal statistics for written bytes
- [#17213](https://github.com/influxdata/telegraf/pull/17213) `outputs.nats` Allow providing a subject layout
- [#17346](https://github.com/influxdata/telegraf/pull/17346) `outputs.nats` Enable batch serialization with use_batch_format
- [#17249](https://github.com/influxdata/telegraf/pull/17249) `outputs.sql` Allow sending batches of metrics in transactions
- [#17510](https://github.com/influxdata/telegraf/pull/17510) `parsers.avro` Support record arrays at root level
- [#17365](https://github.com/influxdata/telegraf/pull/17365) `plugins.snmp` Allow debug logging in gosnmp
- [#17345](https://github.com/influxdata/telegraf/pull/17345) `selfstat` Implement collection of plugin-internal statistics
### Bugfixes
- [#17411](https://github.com/influxdata/telegraf/pull/17411) `inputs.diskio` Handle counter wrapping in io fields
- [#17551](https://github.com/influxdata/telegraf/pull/17551) `inputs.s7comm` Use correct value for string length with 'extra' parameter
- [#17579](https://github.com/influxdata/telegraf/pull/17579) `internal` Extract go version more robustly
- [#17566](https://github.com/influxdata/telegraf/pull/17566) `outputs` Retrigger batch-available-events only if at least one metric was written successfully
- [#17381](https://github.com/influxdata/telegraf/pull/17381) `packaging` Rename rpm from loong64 to loongarch64
### Dependency Updates
- [#17519](https://github.com/influxdata/telegraf/pull/17519) `deps` Bump cloud.google.com/go/storage from 1.56.0 to 1.56.1
- [#17532](https://github.com/influxdata/telegraf/pull/17532) `deps` Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.18.2 to 1.19.0
- [#17494](https://github.com/influxdata/telegraf/pull/17494) `deps` Bump github.com/SAP/go-hdb from 1.13.12 to 1.14.0
- [#17488](https://github.com/influxdata/telegraf/pull/17488) `deps` Bump github.com/antchfx/xpath from 1.3.4 to 1.3.5
- [#17540](https://github.com/influxdata/telegraf/pull/17540) `deps` Bump github.com/aws/aws-sdk-go-v2/config from 1.31.0 to 1.31.2
- [#17538](https://github.com/influxdata/telegraf/pull/17538) `deps` Bump github.com/aws/aws-sdk-go-v2/credentials from 1.18.4 to 1.18.6
- [#17517](https://github.com/influxdata/telegraf/pull/17517) `deps` Bump github.com/aws/aws-sdk-go-v2/feature/ec2/imds from 1.18.3 to 1.18.4
- [#17528](https://github.com/influxdata/telegraf/pull/17528) `deps` Bump github.com/aws/aws-sdk-go-v2/service/cloudwatch from 1.48.0 to 1.48.2
- [#17536](https://github.com/influxdata/telegraf/pull/17536) `deps` Bump github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs from 1.56.0 to 1.57.0
- [#17524](https://github.com/influxdata/telegraf/pull/17524) `deps` Bump github.com/aws/aws-sdk-go-v2/service/dynamodb from 1.46.0 to 1.49.1
- [#17493](https://github.com/influxdata/telegraf/pull/17493) `deps` Bump github.com/aws/aws-sdk-go-v2/service/ec2 from 1.242.0 to 1.244.0
- [#17527](https://github.com/influxdata/telegraf/pull/17527) `deps` Bump github.com/aws/aws-sdk-go-v2/service/ec2 from 1.244.0 to 1.246.0
- [#17530](https://github.com/influxdata/telegraf/pull/17530) `deps` Bump github.com/aws/aws-sdk-go-v2/service/kinesis from 1.38.0 to 1.39.1
- [#17534](https://github.com/influxdata/telegraf/pull/17534) `deps` Bump github.com/aws/aws-sdk-go-v2/service/sts from 1.37.0 to 1.38.0
- [#17513](https://github.com/influxdata/telegraf/pull/17513) `deps` Bump github.com/aws/aws-sdk-go-v2/service/timestreamwrite from 1.34.0 to 1.34.2
- [#17514](https://github.com/influxdata/telegraf/pull/17514) `deps` Bump github.com/coreos/go-systemd/v22 from 22.5.0 to 22.6.0
- [#17563](https://github.com/influxdata/telegraf/pull/17563) `deps` Bump github.com/facebook/time from 0.0.0-20240626113945-18207c5d8ddc to 0.0.0-20250903103710-a5911c32cdb9
- [#17526](https://github.com/influxdata/telegraf/pull/17526) `deps` Bump github.com/gophercloud/gophercloud/v2 from 2.7.0 to 2.8.0
- [#17537](https://github.com/influxdata/telegraf/pull/17537) `deps` Bump github.com/microsoft/go-mssqldb from 1.9.2 to 1.9.3
- [#17490](https://github.com/influxdata/telegraf/pull/17490) `deps` Bump github.com/nats-io/nats-server/v2 from 2.11.7 to 2.11.8
- [#17523](https://github.com/influxdata/telegraf/pull/17523) `deps` Bump github.com/nats-io/nats.go from 1.44.0 to 1.45.0
- [#17492](https://github.com/influxdata/telegraf/pull/17492) `deps` Bump github.com/safchain/ethtool from 0.5.10 to 0.6.2
- [#17486](https://github.com/influxdata/telegraf/pull/17486) `deps` Bump github.com/snowflakedb/gosnowflake from 1.15.0 to 1.16.0
- [#17541](https://github.com/influxdata/telegraf/pull/17541) `deps` Bump github.com/tidwall/wal from 1.1.8 to 1.2.0
- [#17529](https://github.com/influxdata/telegraf/pull/17529) `deps` Bump github.com/vmware/govmomi from 0.51.0 to 0.52.0
- [#17496](https://github.com/influxdata/telegraf/pull/17496) `deps` Bump go.opentelemetry.io/collector/pdata from 1.36.1 to 1.38.0
- [#17533](https://github.com/influxdata/telegraf/pull/17533) `deps` Bump go.opentelemetry.io/collector/pdata from 1.38.0 to 1.39.0
- [#17516](https://github.com/influxdata/telegraf/pull/17516) `deps` Bump go.step.sm/crypto from 0.69.0 to 0.70.0
- [#17499](https://github.com/influxdata/telegraf/pull/17499) `deps` Bump golang.org/x/mod from 0.26.0 to 0.27.0
- [#17497](https://github.com/influxdata/telegraf/pull/17497) `deps` Bump golang.org/x/net from 0.42.0 to 0.43.0
- [#17487](https://github.com/influxdata/telegraf/pull/17487) `deps` Bump google.golang.org/api from 0.246.0 to 0.247.0
- [#17531](https://github.com/influxdata/telegraf/pull/17531) `deps` Bump google.golang.org/api from 0.247.0 to 0.248.0
- [#17520](https://github.com/influxdata/telegraf/pull/17520) `deps` Bump google.golang.org/grpc from 1.74.2 to 1.75.0
- [#17518](https://github.com/influxdata/telegraf/pull/17518) `deps` Bump google.golang.org/protobuf from 1.36.7 to 1.36.8
- [#17498](https://github.com/influxdata/telegraf/pull/17498) `deps` Bump k8s.io/client-go from 0.33.3 to 0.33.4
- [#17515](https://github.com/influxdata/telegraf/pull/17515) `deps` Bump super-linter/super-linter from 8.0.0 to 8.1.0
## v1.35.4 {date="2025-08-18"}
### Bugfixes
@ -5973,14 +6051,14 @@ for details about the mapping.
### New input data formats (parsers)
- [csv](https://archive.docs.influxdata.com/telegraf/v1/data_formats/input/csv) - Contributed by @maxunt
- [grok](https://archive.docs.influxdata.com/telegraf/v1/data_formats/input/grok/) - Contributed by @maxunt
- [logfmt](https://archive.docs.influxdata.com/telegraf/v1/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
- [wavefront](https://archive.docs.influxdata.com/telegraf/v1/data_formats/input/wavefront/) - Contributed by @puckpuck
- [csv](https://docs.influxdata.com/telegraf/v1/data_formats/input/csv/) - Contributed by @maxunt
- [grok](https://docs.influxdata.com/telegraf/v1/data_formats/input/grok/) - Contributed by @maxunt
- [logfmt](https://docs.influxdata.com/telegraf/v1/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
- [wavefront](https://docs.influxdata.com/telegraf/v1/data_formats/input/wavefront/) - Contributed by @puckpuck
### New output data formats (serializers)
- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1/data_formats/output/splunkmetric/) - Contributed by @ronnocol
- [splunkmetric](https://docs.influxdata.com/telegraf/v1/data_formats/output/splunkmetric/) - Contributed by @ronnocol
### Features
@ -6761,7 +6839,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
- Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
- Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
- Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1/concepts/data_formats_input/#collectd).
- Add [collectd parser](https://docs.influxdata.com/telegraf/v1/data_formats/input/collectd/).
- Simplify plugin testing without outputs.
- Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
- Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.

View File

@ -6,7 +6,7 @@ influxdb3_core:
versions: [core]
list_order: 2
latest: core
latest_patch: 3.4.1
latest_patch: 3.4.2
placeholder_host: localhost:8181
ai_sample_questions:
- How do I install and run InfluxDB 3 Core?
@ -21,7 +21,7 @@ influxdb3_enterprise:
versions: [enterprise]
list_order: 2
latest: enterprise
latest_patch: 3.4.1
latest_patch: 3.4.2
placeholder_host: localhost:8181
ai_sample_questions:
- How do I install and run InfluxDB 3 Enterprise?
@ -100,7 +100,7 @@ influxdb:
latest: v2.7
latest_patches:
v2: 2.7.12
v1: 1.11.8
v1: 1.12.2
latest_cli:
v2: 2.7.5
ai_sample_questions:
@ -141,9 +141,9 @@ telegraf:
menu_category: other
list_order: 6
versions: [v1]
latest: v1.35
latest: v1.36
latest_patches:
v1: 1.35.4
v1: 1.36.0
ai_sample_questions:
- How do I install and configure Telegraf?
- How do I write a custom Telegraf plugin?
@ -183,9 +183,9 @@ enterprise_influxdb:
menu_category: self-managed
list_order: 5
versions: [v1]
latest: v1.11
latest: v1.12
latest_patches:
v1: 1.11.8
v1: 1.12.2
ai_sample_questions:
- How can I configure my InfluxDB v1 Enterprise server?
- How do I replicate data between InfluxDB v1 Enterprise and OSS?

View File

@ -502,8 +502,8 @@ input:
Docker containers.
> [!NOTE]
> Make sure Telegraf has sufficient permissions to access the
> configured endpoint.
> Make sure Telegraf has sufficient permissions to access the configured
> endpoint.
introduced: v0.1.9
os_support: [freebsd, linux, macos, solaris, windows]
tags: [containers]
@ -515,9 +515,9 @@ input:
Docker containers.
> [!NOTE]
> This plugin works only for containers with the `local` or `json-file` or
> `journald` logging driver. Please make sure Telegraf has sufficient
> permissions to access the configured endpoint.
> This plugin works only for containers with the `local`, `json-file`, or
> `journald` logging driver. Make sure Telegraf has sufficient permissions
> to access the configured endpoint.
introduced: v1.12.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [containers, logging]
@ -1970,6 +1970,11 @@ input:
This service plugin receives traces, metrics, logs and profiles from
[OpenTelemetry](https://opentelemetry.io) clients and compatible agents
via gRPC.
> [!NOTE]
> Telegraf v1.32 through v1.35 support the Profiles signal using the **v1
> experimental API**. Telegraf v1.36+ supports the Profiles signal using the
> **v1 development API**.
introduced: v1.19.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [logging, messaging]
@ -2672,6 +2677,19 @@ input:
introduced: v0.3.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [testing]
- name: Turbostat
id: turbostat
description: |
This service plugin monitors system performance using the
[turbostat](https://github.com/torvalds/linux/tree/master/tools/power/x86/turbostat)
command.
> [!IMPORTANT]
> This plugin requires the `turbostat` executable to be installed on the
> system.
introduced: v1.36.0
os_support: [linux]
tags: [hardware, system]
- name: Twemproxy
id: twemproxy
description: |
@ -2835,7 +2853,8 @@ input:
description: |
This plugin provides information about
[X.509](https://en.wikipedia.org/wiki/X.509) certificates accessible e.g.
via local file, tcp, udp, https or smtp protocols.
via local file, tcp, udp, https or smtp protocols and the Windows
Certificate Store.
> [!NOTE]
> When using a UDP address as a certificate source, the server must
@ -2940,8 +2959,8 @@ output:
Explorer](https://docs.microsoft.com/en-us/azure/data-explorer), [Azure
Synapse Data
Explorer](https://docs.microsoft.com/en-us/azure/synapse-analytics/data-explorer/data-explorer-overview),
and [Real-Time Intelligence in
Fabric](https://learn.microsoft.com/fabric/real-time-intelligence/overview)
and [Real time analytics in
Fabric](https://learn.microsoft.com/en-us/fabric/real-time-analytics/overview)
services.
Azure Data Explorer is a distributed, columnar store, purpose built for
@ -3299,9 +3318,17 @@ output:
- name: Microsoft Fabric
id: microsoft_fabric
description: |
This plugin writes metrics to [Real time analytics in
Fabric](https://learn.microsoft.com/en-us/fabric/real-time-analytics/overview)
services.
This plugin writes metrics to [Fabric
Eventhouse](https://learn.microsoft.com/fabric/real-time-intelligence/eventhouse)
and [Fabric
Eventstream](https://learn.microsoft.com/fabric/real-time-intelligence/event-streams/overview?tabs=enhancedcapabilities)
artifacts of [Real-Time Intelligence in Microsoft
Fabric](https://learn.microsoft.com/fabric/real-time-intelligence/overview).
Real-Time Intelligence is a SaaS service in Microsoft Fabric that allows
you to extract insights and visualize data in motion. It offers an
end-to-end solution for event-driven scenarios, streaming data, and data
logs.
introduced: v1.35.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [datastore]
@ -4026,6 +4053,17 @@ processor:
introduced: v1.15.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [annotation]
- name: Round
id: round
description: |
This plugin rounds numerical field values to the configured
precision. This is particularly useful in combination with the [dedup
processor](/telegraf/v1/plugins/#processor-dedup) to reduce the number of
metrics sent to the output when a lower precision is required for the
values.
introduced: v1.36.0
os_support: [freebsd, linux, macos, solaris, windows]
tags: [transformation]
- name: S2 Geo
id: s2geo
description: |
@ -4122,7 +4160,7 @@ processor:
- name: Template
id: template
description: |
This plugin applies templates to metrics for generatuing a new tag. The
This plugin applies templates to metrics for generating a new tag. The
primary use case of this plugin is to create a tag that can be used for
dynamic routing to multiple output plugins or using an output specific
routing option.

View File

@ -29,7 +29,7 @@
"winston": "^3.16.0"
},
"dependencies": {
"axios": "^1.8.4",
"axios": "^1.12.0",
"gray-matter": "^4.0.3",
"jquery": "^3.7.1",
"js-cookie": "^3.0.5",

View File

@ -926,10 +926,10 @@ axe-core@^4.10.0:
resolved "https://registry.yarnpkg.com/axe-core/-/axe-core-4.10.3.tgz#04145965ac7894faddbac30861e5d8f11bfd14fc"
integrity sha512-Xm7bpRXnDSX2YE2YFfBk2FnF0ep6tmG7xPh8iHee8MIcrgq762Nkce856dYtJYLkuIoYZvGfTs/PbZhideTcEg==
axios@^1.4.0, axios@^1.8.4:
version "1.11.0"
resolved "https://registry.yarnpkg.com/axios/-/axios-1.11.0.tgz#c2ec219e35e414c025b2095e8b8280278478fdb6"
integrity sha512-1Lx3WLFQWm3ooKDYZD1eXmoGO9fxYQjrycfHFC8P0sCfQVXyROp0p9PFWBehewBOdCwHc+f/b8I0fMto5eSfwA==
axios@^1.12.0, axios@^1.4.0:
version "1.12.0"
resolved "https://registry.yarnpkg.com/axios/-/axios-1.12.0.tgz#11248459be05a5ee493485628fa0e4323d0abfc3"
integrity sha512-oXTDccv8PcfjZmPGlWsPSwtOJCZ/b6W5jAMCNcfwJbCzDckwG0jrYJFaWH1yvivfCXjVzV/SPDEhMB3Q+DSurg==
dependencies:
follow-redirects "^1.15.6"
form-data "^4.0.4"