| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Don't log errors propogated from send_event
|
| | |
|
|\ \
| |/
|/| |
Fix state group storage bug in workers
|
|/
|
|
|
| |
We needed to move `_count_state_group_hops_txn` to the
StateGroupWorkerStore.
|
|\
| |
| | |
purge_history cleanups
|
| |
| |
| |
| | |
apparently sqlite insists on indexes being named
|
| |
| |
| |
| |
| | |
apparently creating a temporary table commits the transaction. because that's a
useful thing.
|
| |
| |
| |
| |
| | |
event_push_actions doesn't have an index on event_id, so we need to specify
room_id.
|
| |
| |
| |
| |
| | |
... which should speed things up by reducing the amount of data being shuffled
across the connection
|
|\ \
| | |
| | | |
switch back from GIST to GIN indexes
|
| | | |
|
| |\ \ |
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
we can reuse the same code as is used for event insert, for doing the
background index population.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add some comments and improve exception handling when twiddling work_mem for
the search update
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... as a precursor to making event storing and doing the bg update share some
code.
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
see https://github.com/matrix-org/synapse/issues/2753 for details
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We're up to schema v47 on develop now, so this will have to go in there to have
an effect.
This might cause an error if somebody has already run it in the v46 guise, and
runs it again in the v47 guise, because it will cause a duplicate entry in the
bbackground_updates table. On the other hand, the entry is removed once it is
complete, and it is unlikely that anyone other than matrix.org has run it on
v46. The update itself is harmless to re-run because it deliberately copes with
the index already existing.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
People may have queued updates for this, so we can't just delete it.
|
| | | | | | |
|
| |/ / / / |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Create a worker for event creation
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
As we want to have it run on the main synapse instance
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
(we don't just remove remote events)
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Use StateResolutionHandler to resolve state in persist_events
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
... and thus benefit (hopefully) from its cache.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
rejig the if statements to simplify the logic and reduce indentation
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* It's supposed to be purge_local_events, not ..._history
* Fix the doc to have valid json
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | | |
Allow use of higher versions of saml2
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The package was pinned to <4.0 with 07cf96eb because "from saml2 import
config" did not work. This seems to have been fixed in the mean time in the
saml2 package and therefore should not stop to use a more recent version.
Signed-off-by: Oliver Kurz <okurz@suse.de>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Tell storage providers about new file so they can upload
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
delete_local_events for purge_room_history
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
... to avoid locking the table for too long
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Add a flag which makes the purger delete local events
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
it was a bit of a non-sequitur there
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
this thing takes ages and the only sign of any progress is the logs, so having
some logs is useful.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
(beacause it deletes more than state)
|
|\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | / / /
| | |_|_|/ / /
| |/| | | | | |
Remove pointless ratelimit check
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The intention was for the check to be called as early as possible in the
request, but actually was called just before the main ratelimit check,
so was fairly pointless.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Split event creation into a separate handler
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* Split state group persist into seperate storage func
* Add per database engine code for state group id gen
* Move store_state_group to StateReadStore
This allows other workers to use it, and so resolve state.
* Hook up store_state_group
* Fix tests
* Rename _store_mult_state_groups_txn
* Rename StateGroupReadStore
* Remove redundant _have_persisted_state_group_txn
* Update comments
* Comment compute_event_context
* Set start val for state_group_id_seq
... otherwise we try to recreate old state groups
* Update comments
* Don't store state for outliers
* Update comment
* Update docstring as state groups are ints
|
|\ \ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
Remove redundant return value from _calculate_state_delta
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
we already have the state from _get_new_state_after_events, so returning it
from _calculate_state_delta is just confusing.
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Factor out common code for search insert
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
we can reuse the same code as is used for event insert, for doing the
background index population.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
... as a precursor to making event storing and doing the bg update share some
code.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
montoring metrics for number of cache evictions
|
| | |_|_|/
| |/| | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Ensure media is in local cache before thumbnailing
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Handle url_previews with no content-type
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
avoid failing with an exception if the remote server doesn't give us a
Content-Type header.
Also, clean up the exception handling a bit.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Factor out resolve_state_groups to a separate handler
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We extract the storage-independent bits of the state group resolution out to a
separate functiom, and stick it in a new handler, in preparation for its use
from the storage layer.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(to make way for a method that actually just does the state group resolution)
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
factor _get_new_state_after_events out of _calculate_state_delta
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
This reduces the scope of a bunch of variables
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Docstring fixes
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Fix a couple of errors in docstrings
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The return type was a complete lie, so fix it
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
Add an admin route to get all the media in a room
|
| |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
Fix sql error in quarantine_media
|
| | |/ / / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Remove spurious log argument
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
... which would cause scary-looking and unhelpful errors in the log on dns fail
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Remove unused "event_type" param on state.get_current_state_ids
|
| | | | | | | | |
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
this param doesn't seem to be used, and is a bit pointless anyway because it
can easily be replicated by the caller. It is also horrible, because it changes
the return type of the method.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
matrix-org/rav/better_persist_event_exception_handling
Improve exception handling in persist_event
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
1. use `deferred.errback()` instead of `deferred.errback(e)`, which means that
a Failure object will be constructed using the current exception state,
*including* its stack trace - so the stack trace is saved in the Failure,
leading to better exception reports.
2. Set `consumeErrors=True` on the ObservableDeferred, because we know that
there will always be at least one observer - which avoids a spurious "CRITICAL:
unhandled exception in Deferred" error in the logs
|
|\ \ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
Logging and metrics for the http pusher
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use a connection pool for the SimpleHttpClient
|
| |/ / / / / / |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In particular I hope this will help the pusher, which makes many requests to
sygnal, and is currently negotiating SSL for each one.
|
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix SQL for user search
|
| | | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
fix some syntax errors for user search when search_all_users is enabled
fixes #2801, hopefully
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Make it possible to run tests against postgres
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
... instead of creating our own special SQLiteMemoryDbPool, whose purpose was a
bit of a mystery.
For some reason this makes one of the tests run slightly slower, so bump the
sleep(). Sorry.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Configure the connectionpool used for unit tests to run the `on_new_connection`
function.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Remove unused/bitrotted MemoryDataStore
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This isn't used, and looks thoroughly bitrotted.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Factor out get_db_conn to HomeServer base class
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This function is identical to all subclasses, so we may as well push it up to
the base class to reduce duplication (and make use of it in the tests)
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
matrix-org/fix_server_500_on_public_rooms_call_when_no_rooms_exist
Fix server 500 on public rooms call when no rooms exist
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
xrange step argument being 0
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
rooms is zero, the specific cause is due to xrange trying to use a step value of zero, but if the total room number really is zero then it makes sense to just bail and save the extra processing
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add some comments about the reactor tick time metric
|
| | | | | | | | |
|
| |/ / / / / /
|/| | | | | |
| | | | | | | |
blindly implement ?ts for AS. untested
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Matthew's fixes to the unit tests
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Extracted from https://github.com/matrix-org/synapse/pull/2820
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add federation_domain_whitelist
gives a way to restrict which domains your HS is allowed to federate with.
useful mainly for gracefully preventing a private but internet-connected HS from trying to federate to the wider public Matrix network
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
add registrations_require_3pid and allow_local_3pids
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* [ ] split config options into allowed_local_3pids and registrations_require_3pid
* [ ] simplify and comment logic for picking registration flows
* [ ] fix docstring and move check_3pid_allowed into a new util module
* [ ] use check_3pid_allowed everywhere
@erikjohnston PTAL
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
lets homeservers specify a whitelist for 3PIDs that users are allowed to associate with.
Typically useful for stopping people from registering with non-work emails
|
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
These are ids anyways, not mxc uris.
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
This is intended to be used by administrators to monitor the media that is passing through their server, if they wish.
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use the right path for url_preview thumbnails
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This was introduced by #2627: we were overwriting the original media for url
previews with the thumbnails :/
(fixes https://github.com/vector-im/riot-web/issues/6012, hopefully)
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Make storage providers configurable
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
Add decent impl of a FileConsumer
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Twisted core doesn't have a general purpose one, so we need to write one
ourselves.
Features:
- All writing happens in background thread
- Supports both push and pull producers
- Push producers get paused if the consumer falls behind
|
| | | | | | |
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | | |
Fix bugs in block metrics
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
... which I introduced in #2785
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
better exception logging in callbackmetrics
|
| | | | |
| | | | |
| | | | |
| | | | | |
when we fail to render a metric, give a clue as to which metric it was
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Log room when doing state resolution
|
| | | | |
| | | | |
| | | | |
| | | | | |
Mostly because it helps figure out what is prompting the resolution
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Keep track of last access time for local media
|
| | | | | | |
|
| | | | | | |
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
fix SQL when searching all users
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Split resolve_events into two functions
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
... so that the return type doesn't depend on the arg types
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Track DB scheduling delay per-request
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
For each request, track the amount of time spent waiting for a db
connection. This entails adding it to the LoggingContext and we may as well add
metrics for it while we are passing.
|
| |\ \ \ \ \ \ |
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
Sanity checking for user ids
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Check the user_id passed to a couple of APIs for validity, to avoid
"IndexError: list index out of range" exception which looks scary and results
in a 500 rather than a more useful error.
Fixes #1432, among other things
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Track db txn time in millisecs
|
| |\| | | | | | |
| | |_|/ / / / /
| |/| | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
... to reduce the amount of floating-point foo we do.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Fix 'NoneType' object has no attribute 'writeHeaders'
|
| |\ \ \ \ \ \ \ \
| | | |/ / / / / /
| | |/| | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Avoid throwing a (harmless) exception when we try to write an error response to
an http request where the client has disconnected.
This comes up as a CRITICAL error in the logs which tends to mislead people
into thinking there's an actual problem
|
|\ \ \ \ \ \ \ \ \
| |_|/ / / / / / /
|/| | | | | | | | |
rework runInteraction in terms of runConnection
|
| |\ \ \ \ \ \ \ \
| |/ / / / / / / /
|/| | | / / / / /
| | |_|/ / / / /
| |/| | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|_|/ / / /
|/| | | | | | | |
Optimise LoggingContext creation and copying
|
| |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | / / / /
| | |_|/ / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix thumbnailing remote files
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |_|_|/ / / /
|/| | | | | | |
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It turns out that the only thing we use the __dict__ of LoggingContext for is
`request`, and given we create lots of LoggingContexts and then copy them every
time we do a db transaction or log line, using the __dict__ seems a bit
redundant. Let's try to optimise things by making the request attribute
explicit.
|
| |/ / / /
|/| | | |
| | | | |
| | | | | |
... so that we can share the code
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Reorganise request and block metrics
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In order to circumvent the number of duplicate foo:count metrics increasing
without bounds, it's time for a rearrangement.
The following are all deprecated, and replaced with synapse_util_metrics_block_count:
synapse_util_metrics_block_timer:count
synapse_util_metrics_block_ru_utime:count
synapse_util_metrics_block_ru_stime:count
synapse_util_metrics_block_db_txn_count:count
synapse_util_metrics_block_db_txn_duration:count
The following are all deprecated, and replaced with synapse_http_server_response_count:
synapse_http_server_requests
synapse_http_server_response_time:count
synapse_http_server_response_ru_utime:count
synapse_http_server_response_ru_stime:count
synapse_http_server_response_db_txn_count:count
synapse_http_server_response_db_txn_duration:count
The following are renamed (the old metrics are kept for now, but deprecated):
synapse_util_metrics_block_timer:total ->
synapse_util_metrics_block_time_seconds
synapse_util_metrics_block_ru_utime:total ->
synapse_util_metrics_block_ru_utime_seconds
synapse_util_metrics_block_ru_stime:total ->
synapse_util_metrics_block_ru_stime_seconds
synapse_util_metrics_block_db_txn_count:total ->
synapse_util_metrics_block_db_txn_count
synapse_util_metrics_block_db_txn_duration:total ->
synapse_util_metrics_block_db_txn_duration_seconds
synapse_http_server_response_time:total ->
synapse_http_server_response_time_seconds
synapse_http_server_response_ru_utime:total ->
synapse_http_server_response_ru_utime_seconds
synapse_http_server_response_ru_stime:total ->
synapse_http_server_response_ru_stime_seconds
synapse_http_server_response_db_txn_count:total ->
synapse_http_server_response_db_txn_count
synapse_http_server_response_db_txn_duration:total
synapse_http_server_response_db_txn_duration_seconds
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix a logcontext leak in persist_events
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ObserveableDeferred expects its callbacks to be called without any
logcontexts, whereas it turns out we were calling them with the logcontext of
the request which initiated the persistence loop.
It seems wrong that we are attributing work done in the persistence loop to the
request that happened to initiate it, so let's solve this by dropping the
logcontext for it.
(I'm not sure this actually causes any real problems other than messages in the
debug log, but let's clean it up anyway)
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Metrics for events processed in appservice and fed sender
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
More metrics I wished I'd had
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Metrics for number of RDATA commands received
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
I found myself wishing we had this.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Refactor MediaRepository to separate out storage
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
erikj/media_storage_refactor
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Make Counter render floats
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prometheus handles all metrics as floats, and sometimes we store non-integer
values in them (notably, durations in seconds), so let's render them as floats
too.
(Note that the standard client libraries also treat Counters as floats.)
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Reinstate media download on thumbnail request
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
We need to actually download the remote media when we get a request for a
thumbnail.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
When using synctl with workers, don't start the main synapse automatically
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Add /room/{id}/event/{id} to synapse
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Turns out that there is a valid usecase for retrieving event by id (notably
having received a push), but event ids should be scoped to room, so /event/{id}
is wrong.
|
|\ \ \ \ \ |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|