[Bug]: Various Events Tab issues

[ralphm]

Bug description

- [ ] https://github.com/netdata/netdata-cloud/issues/880
- [x] Cloud: missing facet on Context
- [ ] https://github.com/netdata/netdata-cloud/issues/888
- [ ] https://github.com/netdata/netdata-cloud/issues/886
- [x] Local: Time filter not applied
- [x] Local: Timestamps are not monotonically decreasing and repeat when scrolling
- [ ] Local: Missing histogram
- [x] Local: Alert Status is not mapped according to display names
- [ ] Local: Missing Event Type facet (even though there's only one right now)
- [x] Local: Instance Name is called Chart Name in Cloud
- [x] Local: Order of facets should be respected (Alert Name then Chart Name)

Expected behavior

Steps to reproduce

Screenshots

No response

Error Logs

No response

Desktop

No response

Additional context

No response

[novykh]

What's this? Cloud: missing facet on Context

[ralphm]

What's this? Cloud: missing facet on Context

Cloud doesn't provide a facet on Netdata.context.name right now.

[novykh]

• The local dashboard events have a different mechanism to cloud events. That said, facets are not the same we are showing what the agent is sending.
• The issue regarding timestamps (changing datetime and refresh the page will be fixed in next release)
• Not sure where this at: Local: Instance Name is called Chart Name in Cloud

[hugovalente-pm]

@novykh @ralphm tried to assess how things were on this bug

The local dashboard events have a different mechanism to cloud events. That said, facets are not the same we are showing what the agent is sending.

Knowing this as a fact, do we consider this something we need to "live with"?

The issue regarding timestamps (changing datetime and refresh the page will be fixed in next release)

Not everything was fixed, left this comment on the ticket dedicated to this #886 (comment)

Not sure where this at: Local: Instance Name is called Chart Name in Cloud

this is the same on both now

Cloud	Local