Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix misspelling of anomaly #49

Closed
andrewkroh opened this issue Nov 7, 2018 · 0 comments · Fixed by #67
Closed

Fix misspelling of anomaly #49

andrewkroh opened this issue Nov 7, 2018 · 0 comments · Fixed by #67

Comments

@andrewkroh
Copy link
Member

See misspellings in https://github.com/elastic/go-libaudit/search?q=anomoly&unscoped_q=anomoly

andrewkroh added a commit to andrewkroh/go-libaudit that referenced this issue Jun 18, 2020
This fixes the spelling of anomaly (misspelled as "anomoly") is several places.

Two constants in Go were changed

- aucoalesce.EventTypeAnomaly
- aucoalesce.EventTypeAnomalyResponse

And the names associated with those constants where changed (affect "category" values in events)

- "anomaly"
- "anomaly-response"

Fixes elastic#49
andrewkroh added a commit to andrewkroh/go-libaudit that referenced this issue Jun 18, 2020
This fixes the spelling of anomaly (misspelled as "anomoly") is several places.

Two constants in Go were changed

- aucoalesce.EventTypeAnomaly
- aucoalesce.EventTypeAnomalyResponse

And the names associated with those constants where changed (affect "category" values in events)

- "anomaly"
- "anomaly-response"

Fixes elastic#49
andrewkroh added a commit that referenced this issue Jun 18, 2020
This fixes the spelling of anomaly (misspelled as "anomoly") is several places.

Two constants in Go were changed

- aucoalesce.EventTypeAnomaly
- aucoalesce.EventTypeAnomalyResponse

And the names associated with those constants where changed (affect "category" values in events)

- "anomaly"
- "anomaly-response"

Fixes #49
renini pushed a commit to renini/go-libaudit that referenced this issue Jun 26, 2024
This fixes the spelling of anomaly (misspelled as "anomoly") is several places.

Two constants in Go were changed

- aucoalesce.EventTypeAnomaly
- aucoalesce.EventTypeAnomalyResponse

And the names associated with those constants where changed (affect "category" values in events)

- "anomaly"
- "anomaly-response"

Fixes elastic#49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant