# InfluxDB and Event Management?

**URL:** https://community.influxdata.com/t/influxdb-and-event-management/16160
**Category:** Dashboards
**Tags:** influxdb, chronograf, grafana
**Created:** [October 1, 2020, 1:44am UTC](https://community.influxdata.com/t/influxdb-and-event-management/16160 "2020-10-01T01:44:05Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![randallnacr](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@randallnacr](https://community.influxdata.com/u/randallnacr)
#### Post date: [October 1, 2020, 1:44am UTC](https://community.influxdata.com/t/influxdb-and-event-management/16160/1 "2020-10-01T01:44:05Z")

</div>

Hello everybody,

I am new to InfluxDB, and currently exploring it to see if we can implement it in our company, I already did some quick testing with Grafana and Chronograf, I love the dashboards and how customizable they are, specially with Chronograf, but I have one question; is there any plugin or way to implement an actual event management with InfluxDB? We are moving from licenses to OSS, on our actual implementation we process syslog, traps, snmp polling, metrics from agents, json events, etc, and all those events are sent to a centralized event viewer that can process alerts (for example critical ones) for a medium to large company, so that a NOC can take action on it or escalate accordingly.

Or does someone has any experience implementing InfluxDB with any other OSS Event Management?

In case I didn’t explain myself correctly, I am talking about something like “Zabbix Problems” or the “Netcool Event Viewer”, see below:

Zabbix Problems:

[https://www.zabbix.com/documentation/4.0/\_detail/manual/web\_interface/problems2.png?id=manual%3Aweb\_interface%3Afrontend\_sections%3Amonitoring%3Aproblems](https://www.zabbix.com/documentation/4.0/_detail/manual/web_interface/problems2.png?id=manual%3Aweb_interface%3Afrontend_sections%3Amonitoring%3Aproblems)

Netcool Event Viewer:

 ![](https://us1.discourse-cdn.com/flex023/uploads/influxdata/original/2X/4/4e2ce0fb43e001fd90dfc8ad598e07d18d3774be.jpeg)

---

<div class="post-metadata">

### Author: ![Anaisdg](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/anaisdg/32/6401_2.png) [@Anaisdg](https://community.influxdata.com/u/Anaisdg)
#### Post date: [October 9, 2020, 2:47pm UTC](https://community.influxdata.com/t/influxdb-and-event-management/16160/2 "2020-10-09T14:47:33Z")

</div>

Hello @randallnacr,  
I’m not sure. Is this useful?  
[https://www.zabbix.com/integrations/influxdb](https://www.zabbix.com/integrations/influxdb)

---

<div class="post-metadata">

### Author: ![tim.hall](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/tim.hall/32/39_2.png) [@tim.hall](https://community.influxdata.com/u/tim.hall)
#### Post date: [October 9, 2020, 4:16pm UTC](https://community.influxdata.com/t/influxdb-and-event-management/16160/3 "2020-10-09T16:16:18Z")

</div>

The log viewer in Chronograf is intended to help in this area. But, it is limited to a specific syslog format and won’t cover SNMP traps, json events, etc.

> **[Analyze logs with Chronograf | Chronograf 1.10 Documentation](https://docs.influxdata.com/chronograf/v1.8/guides/analyzing-logs/)**
>
> Analyze log information using Chronograf.