https://github.com/logicmonitor/lm-logs-okta
https://github.com/logicmonitor/lm-logs-okta
Last synced: 5 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/logicmonitor/lm-logs-okta
- Owner: logicmonitor
- Created: 2023-01-25T08:45:50.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2023-08-02T07:24:25.000Z (almost 3 years ago)
- Last Synced: 2024-12-30T00:13:27.708Z (over 1 year ago)
- Language: Python
- Size: 76.2 KB
- Stars: 0
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# OKTA Log Collector for LM-Logs
This integration provides an AWS cloudformation stack which includes a lambda function periodically collecting Okta system logs and forwarding it to Logicmonitor LM Logs.
## Deploy as CloudFormation stack
[](https://console.aws.amazon.com/cloudformation/home#/stacks/create/review?stackName=lm-okta-log-collector&templateURL=https://lm-logs-okta-collector.s3.amazonaws.com/stable/latest.yaml)
## Parameters
| Parameter | Description | Default |
|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
| FunctionName | The name for lambda function. | LM-Okta-Log-Collector |
| LMCompanyName | The LogicMonitor account name. | - |
| LMAccessId | The LM API tokens access ID | - |
| LMAccessKey | The LM API tokens access key | - |
| LMBearerToken | The LM API Bearer token. (You must specify LMBearerToken if not providing LMAccessId, LMAccessKey. In case you provide all, LMAccessId and LMAccessKey will be used to authenticate with Logicmonitor. ) key | - |
| OktaDomain | Okta domain eg "company.okta.com". | - |
| OktaAPIKey | Okta API key to fetch logs from okta. | - |
| LMLogsServiceName | This will be used for anomaly detection. | okta-system-logs |
| LMResourceId | Ignored when LMLogsServiceName is specified. Is a json for resource mapping. if specified as {\"system.hostname\" : \"prod-node-us-west-1\"} all logs will be mapped against the device with property system.hostname = prod-node-us-west-1 | - |
| IncludeMetadataKeys | comma separated keys to add as event metadata in a lm-log event. for nested json specify '.' eg - actor.displayname,actor.type | 'severity,actor.displayname,actor.type,actor.alternateId,client.geographicalContext.city,displayMessage,eventType' |
| ScheduleExpression | Cron expression for this lambda function. "rate(2 minutes)" means, function will be triggered every 2 minutes. see https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html for more details. | "rate(2 minutes)" |
| FunctionMemorySize | The memory size for the OKTA Log Collector lambda function in MBs | 2048 |
| FunctionTimeoutInSeconds | The timeout for the OKTA Log Collector lambda function in Seconds | 110 |