Skip to content

Events API broken due to missing fluentd config fields #4574

Closed
@andreilee

Description

Your Environment

  • Version: Master
  • Affected Component: Orchestrator
  • Affected Subcomponent: Events
  • Deployment Environment: e.g. AWS (orc8r)

Describe the Issue

It's been found that multiple events API endpoints do not work, specifically

  • events/{network_id}
  • events/{network_id}/count

but that events/{network_id}/{stream_name} does work.

The two broken API endpoints fetch events through an elasticsearch index filter of eventd*, whereas the third, working endpoint does not. We find that one of the fluentd configuration files is not set up correctly for events, specifically output.conf, and all events are indexed with prefix magma instead of eventd

Expected behavior

  • all events APIs should work
  • events should be populated in elasticsearch with index prefix eventd

Screenshots
N/A

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions