Prometheus-operator: Add support docs for Cortex
It would be good to have some documentation on how to use Cortex with the prometheus-operator.
From what I understand all it would take is to add documention on how to configure the RemoteWrite feature in the prometheus-operator to point to an instance of Cortex (or for example Weave Cloud).
cc @brancz
lilic
All 3 comments
A lot of people have asked for RemoteRead and RemoteWrite documentation so I think this could be a nice example. I think we should primarily make this about RemoteRead and RemoteWrite, but I'm fine with having something along the lines of "You will need a service that accepts the RemoteRead/RemoteWrite interface, see the official Prometheus documentation on services that support RemoteRead/RemoteWrite".
If weaveworks can provide an endpoint that needs no signup or anything I'm also happy to include that in the documentation provided weaveworks owns this document and fixes things as they come up. Same goes for other providers cc @tomwilkie @bcotton. Probably a win-win if the user guide is easy to follow.
RE #352
brancz
on 19 Jul 2018
This issue has been automatically marked as stale because it has not had any activity in last 60d. Thank you for your contributions.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 15 Aug 2019
Seems like it is still valid. Right @lilic ? :smile:
paulfantom
on 5 Oct 2020
Related issues
sc250024
路
4Comments
xuchenhao001
路
3Comments
wesselOC
路
4Comments
wkjun
路
3Comments
ohmanandam
路
4Comments
Most helpful comment
A lot of people have asked for
RemoteReadandRemoteWritedocumentation so I think this could be a nice example. I think we should primarily make this aboutRemoteReadandRemoteWrite, but I'm fine with having something along the lines of "You will need a service that accepts theRemoteRead/RemoteWriteinterface, see the official Prometheus documentation on services that supportRemoteRead/RemoteWrite".If weaveworks can provide an endpoint that needs no signup or anything I'm also happy to include that in the documentation provided weaveworks owns this document and fixes things as they come up. Same goes for other providers cc @tomwilkie @bcotton. Probably a win-win if the user guide is easy to follow.
RE #352