elastic / elastic/integrations

[Okta]: Cannot disable fail_on_template_error for HTTPJSON integration when deployed via docker container

Open
#21,027 1 comment 0 reactions 1 assignee Claimed by @brijesh-elastic View on GitHub
Integration:okta needs:triage Team:SDE-Crest Team:Security-Service Integrations
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

Okta [packages/okta]

### Dataset Name

_No response_

### Integration Version

3.14.1

### Agent Version

8.19.18

### Agent Output Type

elasticsearch

### Elasticsearch Version

8.19.18

### OS Version and Architecture

Ubuntu 24.04.4 LTS

### Software/API Version

_No response_

### Error Message

Unit state changed httpjson-default-httpjson-okta-4c40a265-b052-4cde-9b89-e84c5e85bc0b (HEALTHY->DEGRADED): failed to execute template rate-limit_remaining: the template result is empty

### Event Original

_No response_

### What did you do?

Tried to configure the Okta integration on an elastic-agent deployed as a docker container and it's throwing the 'template result is empty' error because the Okta API doesn't return the X-Rate-Limit-Remaining header and the integration always expects it. The workaround I've found says to disable fail_on_template_error but since we are running elastic-agent in a docker container it is not possible to disable via httpjson-okta-system-logs.yaml and there is no advanced YAML editor in the kibana UI for this integration.

### What did you see?

Integration status is degraded with error "failed to execute template rate-limit_remaining: the template result is empty"

### What did you expect to see?

n/a

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.