Okta System Logs Collector source plugin - Chronosphere Documentation

This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.

The Okta System Logs Collector source plugin (name: http_loader, alias: okta_system_logs) lets you ingest data from your Okta instances into a telemetry pipeline. This is a pull-based source plugin.

This plugin doesn’t support the use of a descriptive metadata name in the Pipeline Builder interface.

This plugin doesn’t support duplicates of itself within the same pipeline. Additionally, this plugin can’t be used in combination with these source plugins within the same telemetry pipeline:

Supported telemetry types

The for Chronosphere Telemetry Pipeline supports these telemetry types:

Logs	Metrics	Traces

Configuration parameters

Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

General

Name	Key	Description	Default
Okta Domain URL	`url`	The URL of your Okta domain.	none
Okta API Token	`api_token`	Your Okta API token.	none
Pull Interval	`pull_interval`	The time between each API call in Okta system logs.	`10s`

Advanced

Name	Key	Description	Default
Optional Request body	`body`	Optional request body. For example, `{"custom":"data"}`.	none
Request Timeout	`timeout`	The amount of time between requests.	`10s`
Max Response Bytes	`max_response_bytes`	Whether to limit the amount of bytes to read from the response body.	`1572860`
Memory Buffer Limit	`mem_buf_limit`	Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit’s rules for unit sizes. If unspecified, no limit is enforced. For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet workload type. To learn more, see the v2 backpressure guide. For v3 pipelines, this parameter is independent from the OpenTelemetry `memory_limiter` and `batch` processors.	none

OAuth2

Name	Key	Description	Default
OAuth2 Client ID	`oauth2_client_id`	Optional OAuth 2.0 Client ID. You need to at least pass the client ID, secret and token URL to enable OAuth 2.0 authentication. Uses the `client_credentials` flow.	none
OAuth2 Client Secret	`oauth2_client_secret`	Optional OAuth 2.0 client secret.	none
OAuth2 Token URL	`oauth2_token_url`	Optional OAuth 2.0 token URL in the formal of HTTP or HTTPS. For example, `https://example.org/oauth2/token`.	none
OAuth2 Scopes	`oauth2_scopes`	Optional list of additional scopes for OAuth 2.0 authentication separated by space. For example, `scope1 scope2`.	none
OAuth2 Scopes Separator	`oauth2_scopes_separator`	Additional parameter to pass during OAuth 2.0 authentication that separates scopes specified in OAuth 2.0 Scopes.	none
OAuth2 Additional Params	`oauth2_endpoint_params`	Optional additional parameters to add during OAuth 2.0 authentication. The format is a URL query string. For example, `foo=bar&bar=qux`.	none

​Supported telemetry types

​Configuration parameters

​General

​Advanced

​OAuth2

Supported telemetry types

Configuration parameters

General

Advanced

OAuth2