visualization not working about o365beat HOT 5 CLOSED

Thanks for the issue, I hope we can get things squared away for you. A couple quick questions:

1. Did you run o365beat setup against your elastic instance, before shipping logs, and is kibana running on that same system?
2. Did you make any significant modifications to your o365beat.yml file? If possible, could you add it to this issue (after removing sensitive information like IDs and client secret)?
3. By default, the visualizations should use the default index pattern o365beat-* ... do you have that pattern in kibana?

Thanks again. If you'd rather work through this via email, you can reach me at [email protected].

from o365beat.

from o365beat.

You definitely don't need to install the beat on all the nodes, or even on any of them (it could be running on a separate box, we see it often run on logstash boxes for example).

By default, the o365beat setup command assumes kibana is on localhost:5601, the same as other beats. If you have a more complex setup, you'll need to change your config file accordingly (o365beat.yml). Specifically, you'll need to update setup.kibana.host (which defaults to localhost:5601) and all its supporting settings. You can see these options, commented out, on these lines of the o365beat.reference.yml reference file, and the filebeat docs do a good job of walking through this too ... it generally works the same as o365beat.

If your kibana setup is correct in the config, it's possible your elasticsearch config wasn't. If you send me your (redacted) config file by email, we can sort through any remaining issues. Thanks for your patience!

from o365beat.

from o365beat.

As noted in #43: while researching another issue, I realized (a few months late) that filebeat now supports o365 with an official module, as of v7.7.0. It supports a variety of visualizations out of the box, and will surely stay more current with the latest updates to the Elastic Stack, including Kibana. It's probably the best solution for you going forward, if you haven't already migrated that way.

Given there's an "official solution" to visualization, and their documentation regarding Kibana setups is more thorough, I'm going to close this issue. Apologies that it went unaddressed for so long. Thanks for engaging with the project!

from o365beat.