The Influxdata metrics collection and visualization toolset is an excellent resource in the fedora community to monitor your workspace or server's performance over time.
https://v2.docs.influxdata.com/v2.0/
If interesting to the community I'd like to put together a how-to on setting it up within a fedora instance and show how to create some sample dashboards.
Metadata Update from @glb: - Issue tagged with: article
Hello @glb, @sborza ,
There is still interest in this topic? I wrote a couple of similar articles and could try a new spin on metrics related to a server. Here are the links:
InfluxDB intro Glances and InfluxDB
Let me know and then we can discuss about the scope of the new article.
Thanks.
It looks good to me. Just let us know when it is ready in our WordPress instance and we'll give it a quick review and publish it.
Thanks!
Metadata Update from @rlengland: - Assignee reset
Metadata Update from @rlengland: - Issue assigned to josevnz
I forgot we submit this way back when! With InfluxDB 3.0 on the horizon it would be good to get an article together. The 2.X series is quickly being sunset so an updated set of instructions would be useful.
I think Jose’s would be a good follow-up to an intro one. Or we can look to merge into a single longer article?
@sborza and @josevnz One collaborative article to two, We'll let you two decide. If another article is decided on let us know by opening a new article proposal and we will start a new Pagure ticket to track it. We can make one dependent on the other if you wish.
Hello all,
I had the introductory article ready; It is a first cut as it has some problems:
If you like the content and the overall idea, we can make fixes, launch this as an introductory article and then move on with the monitoring part.
Please let me know what you think, link is below:
https://fedoramagazine.org/?p=38861&preview=true&preview_id=38861
At a glance, this looks OK. I went ahead and fixed the text styling for the code examples (this site requires that you use "preformatted" blocks instead of "code" blocks.
As you noted, the images need to be uploaded to this site.
I'm also not crazy about linking to the third-party asciinema site for you CLI demos. If possible, I would prefer that those were converted to animated SVGs and also uploaded to this site's media library. You can see an example of this being done recently in the TransFLAC article (he used termtosvg to create the animated SVG).
I'll start uploading the images, will post here once done.
I need to read about the animated SVG. To me, it defeats the purpose of having a terminal session recorded (and the comments on the article point out to many drawbacks), but I will give it a try before pushing further back.
Metadata Update from @rlengland: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=38861&preview=true&preview_id=38861 - Issue tagged with: needs-image
I uploaded all the images, working on the ASCIINEMA conversions now.
Also finished converting the ASCIINEMA to SVG. Article is complete I think, please review.
If the introductory article looks good then we can move on a monitoring article, and cover improvements on the 3.0 version there as well (many shops are not ready to move away from 2.xx series because it requires a significant effort).
Thanks for pulling this together so quickly! Is this still the same link? Giving me a 404...
Yes, the link https://fedoramagazine.org/?p=38861&preview=true&preview_id=38861 is correct.
I had to re-authenticate to make it work.
You may want to try the edit link instead: https://fedoramagazine.org/wp-admin/post.php?post=38861&action=edit
I enabled the public preview just in case: https://fedoramagazine.org/?p=38861&preview=1&_ppp=3c252ac16b
Ah, thanks. I'm not allowed to edit the article so will post some comments here later today!
@sborza I made you a co-author. See if you are able to edit the article now. If you prefer to not be an author, let me know and I will adjust.
Hello guys,
What else is needed to get the article out? Do I need to make more corrections/ edits?
Hello guys, What else is needed to get the article out? Do I need to make more corrections/ edits? Thanks.
@josevnz , @sborza is editing the article at the time of this writing. When he is finished I will start the editing process.
A couple of questions @josevnz:
token
token=<your_token_here>
Wrapping Up
Let me know what you think!
@josevnz @sborza I've done a review and edit on the article.
I made some minor wording changes but I did a major rework on the beginning paragraphs so there was an explanation early on about what the article would cover. This is in order to draw any interested readers into the article.
I also added at "Tip" item which reader may select to be told that they will have to view some of the images in a new window or tab since they are relatively small. We can rework or eliminate that if you desire.
Please take what ever time you need to review and comment or add further information.
Thanks for your work on this article.
This looks good to me, thanks again for the edits @rlengland. Hope you agree @josevnz.
@sborza:
the python code is current, correct?
Code works as expected.
I know it's a contrived example but maybe we should remove any reference to the token...
No, it is obvious enough than a authentication token looks like this. Reader will definitely get the point.
@rlengland, @sborza: I agree with the edits and the article looks very nice, thanks. Also thanks for the cover image.
I'm ready to ship the article and let the readers have fun with it.
Let's do this!
@josevnz @sborza Publication set for 6 October 08:00 UTC. Thanks for all your work on this article!
Hello @sborza , @rlengland
I the article is live. Epic, looks great.
I think the part II of the article can focus now on:
Thanks a lot for all your work, I'm looking forward to collaborate more here.
Issue status updated to: Closed (was: Open) Issue close_status updated to: published
Login to comment on this ticket.