Cross-post Dask observability post #168
Conversation
✅ Deploy Preview for dask-blog ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Thanks @scharlottej13. I love the general intent of this post. However, the post interweaves Dask features with Coiled features throughout so I'm not sure it's the best fit for the Dask community blog without some heavy modification. It feels like too much of a Coiled sales pitch in its current format.
I see three options here:
- Rework the post to remove the Coiled-specific content and instead point readers to the Coiled blog version at the end for further reading. I think it's fine to direct folks to Coiled to learn about how Coiled solves this problem after discussing the OSS options and their pros/cons.
- Add a "Sponsored Post" banner at the top to make it clear that this is a Coiled advert. I'm not sure if we want to go down this road in general, but I know it's been discussed before so maybe the Dask Owners need to chat about this.
- We don't cross-post this one
If we want to go with option 1 let me know and I'll go through and review it through that lens. Also happy to chat about the other options, maybe a call would be easier to get into the nuance here?
|
|
||
| When dealing with unexpected issues in a distributed system, you need to understand what and _why_ it happened, how interactions between individual pieces contributed to the problems, and how to avoid them in the future. | ||
| In other words, you need **observability**. | ||
| This article explains what observability is, how Dask implements it, what pain points remain, and how Coiled helps you overcome these. |
There was a problem hiding this comment.
This line especially sets the reader up for a sales pitch.
|
I agree with @jacobtomlinson, in its current form the post does not seem to be appropriate for the Dark blog. I'd personally be up for modifying in into a format that feels less sponsored, but I could use an independent sparring partner to make this a quick piece of work. @jacobtomlinson, would you want to collaborate on this? |
|
Very happy to help. I don't have capacity this week but maybe next week we could chat about this? |
|
Thanks @jacobtomlinson and @hendrikmakait! I'll close this then (and open a new PR for the css changes I suggested, which is what I should have done in the first place 😄) |
@hendrikmakait wrote this for the Coiled blog, but the content is Dask-focused so I think it would be a good fit for cross-posting on blog.dask.org (see dask/community#291 (comment) for some discussion around this, noting we did something similar in #151).
I made no content changes from the original post.
cc @jacobtomlinson