GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:03:45 JST clacke clacke
    Do you personally find any important difference for your use between Kibana and Grafana? Which one do you prefer? (potentially depending on use case)
    In conversation Thursday, 09-Mar-2023 19:03:45 JST from libranet.de permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:03:41 JST clacke clacke
      in reply to
      • Stefan Midjich ꙮ҄
      @stemid A lot happens in ten years when you have software with diverging visions. =)

      libranet.de/display/0b6b25a8-1…

      Kudos for Kibana staying focused on being an Elastic frontend. Maybe the existence of Grafana helped keep them on track.
      In conversation Thursday, 09-Mar-2023 19:03:41 JST permalink

      Attachments


    • Embed this notice
      Stefan Midjich ꙮ҄ (stemid@mastodon.se)'s status on Thursday, 09-Mar-2023 19:03:42 JST Stefan Midjich ꙮ҄ Stefan Midjich ꙮ҄
      in reply to

      @clacke I think you're mistaken. I used kibana pretty much up until I switched to Grafana and I don't see how they could be a fork of each other.

      btw, personal preference is grafana. but that's also because they have a whole open source ecosystem for observability. At work we use Loki, OpenTelemetry and Grafana, all Grafana labs products.

      In conversation Thursday, 09-Mar-2023 19:03:42 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:03:44 JST clacke clacke
      in reply to
      I've been too lazy to look up why the Kibana/Grafana fork happened. Does anyone have a good summary?
      In conversation Thursday, 09-Mar-2023 19:03:44 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:03:50 JST clacke clacke
      in reply to
      • Sven
      @sumh I don't think you posted that in the conversation you intended. =)

      Sounds cool though! I think /e/ is seeing a lot more development than Ubuntu Touch?
      In conversation Thursday, 09-Mar-2023 19:03:50 JST permalink
    • Embed this notice
      Sven (sumh@social.ellih.eu)'s status on Thursday, 09-Mar-2023 19:03:57 JST Sven Sven
      in reply to
      @clacke I will give /e/OS a try on on my #Fairphone4 . Then I will replace #UbuntuTouch. #eOS
      In conversation Thursday, 09-Mar-2023 19:03:57 JST permalink
    • Embed this notice
      التنينوكس (dragnucs@social.touha.me)'s status on Thursday, 09-Mar-2023 19:03:59 JST التنينوكس التنينوكس
      in reply to
      • :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave:

      @selea @clacke https://grafana.com/blog/2019/09/03/the-mostly-complete-history-of-grafana-ux/

      In conversation Thursday, 09-Mar-2023 19:03:59 JST permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        https://twitter.com/grafana
      clacke likes this.
    • Embed this notice
      التنينوكس (dragnucs@social.touha.me)'s status on Thursday, 09-Mar-2023 19:04:00 JST التنينوكس التنينوكس
      in reply to
      • :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave:

      @selea @clacke never even tought they were forks. They are very different.

      In conversation Thursday, 09-Mar-2023 19:04:00 JST permalink
      clacke repeated this.
    • Embed this notice
      :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave: (selea@social.linux.pizza)'s status on Thursday, 09-Mar-2023 19:04:01 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave: :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave:
      in reply to

      @clacke

      Grafana is a fork of kibana? Did not know, they feel so different...

      In conversation Thursday, 09-Mar-2023 19:04:01 JST permalink
    • Embed this notice
      :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave: (selea@social.linux.pizza)'s status on Thursday, 09-Mar-2023 19:04:02 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave: :debian: 𝚜𝚎𝚕𝚎𝚊 :sunwave:
      in reply to

      @clacke

      What fork?

      In conversation Thursday, 09-Mar-2023 19:04:02 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:04:05 JST clacke clacke
      in reply to
      • التنينوكس
      @dragnucs Great read! Thanks!
      In conversation Thursday, 09-Mar-2023 19:04:05 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:04:17 JST clacke clacke
      in reply to
      And now I'm goimg down the rabbit hole of looking at what's the difference between Graphite, InfluxDb, ...

      I played a lot with Nagios and RRDTool and glanced at Cacti at the end of last millennium, and played a little bit with Prometheus the other year, and to me these all seem like basically RRDTool on steroids.

      I'm not saying they're not an improvement, it's not a bad thing to be RRDTool on steroids, but the hype seems to be saying that everything is brand new when everything is iterative improvement on solid concepts.
      In conversation Thursday, 09-Mar-2023 19:04:17 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Thursday, 09-Mar-2023 19:04:18 JST clacke clacke
      in reply to
      And now I'm going down the rabbit hole of looking at what's the difference between Graphite, InfluxDb, ...

      I played a lot with Nagios and RRDTool and glanced at Cacti at the end of last millennium, and played a little bit with Prometheus the other year, and to me these all seem like basically RRDTool on steroids.

      I'm not saying they're not an improvement, it's not a bad thing to be RRDTool on steroids, but the hype seems to be saying that everything is brand new when everything is iterative improvement on solid concepts.
      In conversation Thursday, 09-Mar-2023 19:04:18 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Friday, 10-Mar-2023 09:57:09 JST clacke clacke
      in reply to
      • frox
      @frox I really appreciated how easy Prometheus was to set up. Add a plugin to our flask application, point Prometheus at the metrics endpoint, boom, colorful graphs.

      Definitely light on resources.
      In conversation Friday, 10-Mar-2023 09:57:09 JST permalink
    • Embed this notice
      frox@tooting.ch's status on Friday, 10-Mar-2023 09:57:10 JST frox frox
      in reply to

      @clacke ooooh, I want to know how your explorations go.
      I wanted to deploy a stack to monitor some small selfhosted servers of mine. And was hoping to avoid anything that was overly heavy on resources. Collectd, influxdb and grafana seemed like an option from my browsing

      In conversation Friday, 10-Mar-2023 09:57:10 JST permalink
    • Embed this notice
      lefarfadet (lefarfadet@mstdn.io)'s status on Saturday, 11-Mar-2023 00:35:33 JST lefarfadet lefarfadet
      in reply to

      @clacke
      For me, grafana helps to merge various datasources under one single dashboard. From what i've seen in the wild, in kibana you can only query elasticSearch. With grafana, it's easier to mix data sources. I found also that setting up a dashboard in grafana is somehow easoer than in kibana. I prefer grafana because you can aggregate mysql, elasticsearch and whatnot

      In conversation Saturday, 11-Mar-2023 00:35:33 JST permalink
    • Embed this notice
      clacke (clacke@libranet.de)'s status on Saturday, 11-Mar-2023 00:35:33 JST clacke clacke
      in reply to
      • lefarfadet
      @lefarfadet Yeah, after being less lazy and doing my research I learned that this is basically the difference, that Kibana has a much more specific use case of being an Elastic dashboard and Grafana is the Swiss knife.
      In conversation Saturday, 11-Mar-2023 00:35:33 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.